fix(ci): keep v4 releases from latest - #487
Conversation
Co-authored-by: Cody Olsen <stipsan@users.noreply.github.com>
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit df4873c. Configure here.
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: actions/checkout@v7 | ||
| - run: gh release edit "react-rx@$(node -p "require('./packages/react-rx/package.json').version")" --latest=false |
There was a problem hiding this comment.
Latest badge not restored
Medium Severity
Demoting the v4 GitHub release with --latest=false does not put the v5 release from current back as latest. After changesets creates the v4 release as latest, this edit only clears that flag, so the repo can end up with no latest release instead of preserving the v5 one.
Reviewed by Cursor Bugbot for commit df4873c. Configure here.


Prevent v4 GitHub releases from replacing the v5 release from
currentas the repository's latest release.Because this repository delegates publishing to a reusable workflow, add a dependent v4-only job that checks out the published package version and marks its
react-rx@<version>GitHub release with--latest=false. The job receives only thecontents: writepermission required to edit release metadata.Validation
actionlint .github/workflows/release.ymlpnpm exec oxfmt --check .github/workflows/release.ymlreact-rx@4.2.5release tag