Uh oh!
There was an error while loading. Please reload this page.
fix(ci): unblock release-please and modernize publish workflows - #344
Conversation
- Drop the packages/mcp/package-lock.json extra-file from the release-please config: the file does not exist (packages/mcp is a root workspace member), and a missing extra-file makes release-please's updater fail, which is why SDK/CLI releases stopped being cut automatically. - Bump actions/checkout v4 -> v5 in both publish workflows (v4 targets deprecated Node 20 runners). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Bca2z6b3pMPb3pe911CXAP
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Uh oh!
There was an error while loading. Please reload this page.
SummaryReviewed the release automation changes in Verdict✅ Reviewed — no issues found. The configuration parses successfully, the diff passes formatting checks, and no actionable correctness, security, data-loss, error-handling, compatibility, or concurrency concerns were identified. |
Two defects in the release automation:
packages/mcp/package-lock.jsondoesn't exist (packages/mcp is a root workspace member covered by the root lockfile). A missing extra-file makes release-please's updater fail, which is the likely reason nosdk-v-*/cli-v-*release PRs were being cut automatically (0.4.0 and the CLI release had to be cut by hand). Removed the entry; the remaining four extra-files all exist.actions/checkout@v4in both publish workflows targets deprecated Node 20 runners (CI warns on every run). Bumped to v5.Verified: all remaining extra-file paths exist on main; workflows are otherwise unchanged.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Bca2z6b3pMPb3pe911CXAP
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Greptile Summary
The PR repairs release automation by removing an extra-file target for a nonexistent package-local lockfile and upgrades checkout in both TypeScript publishing workflows.
packages/mcp/package-lock.jsonrelease-please updater.actions/checkout@v4toactions/checkout@v5.Confidence Score: 5/5
The PR appears safe to merge, with no concrete changed-code defect identified.
The publish workflows retain their existing triggers, tag references, and release steps, while the release-please removal aligns its extra-file targets with the repository’s current root-lockfile workspace layout.
Important Files Changed
Reviews (1): Last reviewed commit: "fix(ci): unblock release-please and mode..." | Re-trigger Greptile