Skip to content

fix(ci): keep v4 releases from latest #487

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stipsan merged 1 commit into from
Aug 4, 2026
Merged

fix(ci): keep v4 releases from latest #487

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,3 +18,15 @@ jobs:
contents: read # for checkout
id-token: write # to enable use of OIDC for npm provenance
secrets: inherit
keep-v4-release-from-latest:
name: Keep v4 release from becoming latest
needs: release
if: github.ref_name == 'v4'
permissions:
contents: write
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

@cursor cursor Bot Aug 4, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit df4873c. Configure here.

env:
GH_TOKEN: ${{ github.token }}