Fix/mill cli readme publish status - #60
Conversation
Adds neuralliquid-tarmac-mill-s2s to mystira_oidc_render_audiences alongside the existing nexamesh-coiltrace-web entry, so Tarmac's new OpenIddict client-credentials client (companion PR in phoenixvc/mystira-workspace) can call Mill's LaTeX-render endpoints with a mill.render-scoped token. No dedicated resource audience was minted on the Mystira side, so this client's own client id is the value to allow here, matching the existing CoilTrace precedent. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@celladore/mill@0.1.0 has been on the public npm registry since 2026-08-30; the CLI section still described publication as pending an auth/scope gate. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
JustAGhosT has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (1)
🔇 Additional comments (2)
📝 SummarySummary by CodeRabbit
WalkthroughThe README now documents the public npm publication of Changesnpm publication documentation
Production OIDC configuration
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This change is merge-ready after normal checks and review; no actionable merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
Full details: Title checkExplanation The title clearly identifies the README publication-status correction, which is a primary part of the changeset. It does not mention the OIDC configuration update, but a title does not need to cover every change. Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
1 participant
What does this PR do?
Type of change
Checklist
.envfiles includedRelated issues