Skip to content

fix(ci): remove @semantic-release/git, add sync-versions command#1141

Merged
abueide merged 1 commit intomasterfrom
fix/npm-workspace-protocol
Mar 3, 2026
Merged

fix(ci): remove @semantic-release/git, add sync-versions command#1141
abueide merged 1 commit intomasterfrom
fix/npm-workspace-protocol

Conversation

@abueide
Copy link
Contributor

@abueide abueide commented Mar 3, 2026

Summary

  • Remove @semantic-release/git plugin from release.config.js — eliminates the need to push version bump commits to protected branches
  • Also remove @semantic-release/changelog (was only useful when committing CHANGELOG.md back to repo)
  • Add scripts/sync-versions.sh + devbox sync-versions command to pull latest npm-published versions into package.json on demand
  • Update wiki/release.md to reflect the new process

How it works now

  • Version source of truth: git tags + npm registry (unchanged)
  • Release notes: GitHub Releases via @semantic-release/github (unchanged)
  • package.json versions: synced manually via devbox run --config=shells/devbox-fast.json sync-versions, included in a PR periodically
  • No more pushing directly to protected branches during release

Test plan

  • Merge and run beta release — should succeed without branch protection errors
  • Verify GitHub Releases are still created with release notes
  • Run sync-versions locally to verify it works

🤖 Generated with Claude Code

Remove the @semantic-release/git plugin which pushes version bump
commits and CHANGELOG.md back to the branch. The default github.token
cannot push to protected branches, and this avoids the need for a PAT.

Version source of truth is git tags + npm registry. Add a
sync-versions devbox command to pull latest npm versions into
package.json on demand. Update release docs accordingly.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@abueide abueide merged commit 67bfcf5 into master Mar 3, 2026
5 checks passed
@abueide abueide deleted the fix/npm-workspace-protocol branch March 3, 2026 02:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant