Repository navigation
fix(release): 🐛 Synchronize package version after publication - #75
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8defc33cdf
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
The release workflow publishes a bumped package version but restores package.json afterward, leaving the repository at 4.0.1 while npm latest is 7.0.2. Update the manifest to 7.0.2 and synchronize it automatically after the release queue completes.
Synchronization reads npm latest, starts from the current remote branch, changes only package.json, and pushes a dedicated chore(release) commit. Rejected pushes retry from the updated remote without force-pushing; matching versions are a no-op, while registry failures, invalid versions, and downgrades fail explicitly. The sync commit does not match the legacy release baseline marker or create another release.
Validation: nine release-workflow tests pass, including real local Git remotes, idempotency, preservation of newer commits, concurrent push recovery, registry failure, malformed versions and downgrade protection. Package and documentation builds pass; workflow YAML and Bash syntax checks pass. Independent review found no actionable issues.
Review follow-up: reject concurrent package renames after every checkout, and retain the successfully published version if npm latest is temporarily stale. Both cases have regression tests.