fix(latest): add make_latest property to the GH release PATCH request during publish#1169
Merged
travi merged 2 commits intosemantic-release:masterfrom Feb 12, 2026
Merged
fix(latest): add make_latest property to the GH release PATCH request during publish#1169travi merged 2 commits intosemantic-release:masterfrom
travi merged 2 commits intosemantic-release:masterfrom
Conversation
… during publish It's required to not mark as latest when removing draft status after assets upload
Contributor
Author
@travi I've now added tests 🙏 |
Contributor
Author
|
@pfarnach WDYT? |
travi
approved these changes
Feb 12, 2026
|
🎉 This PR is included in version 12.0.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This was referenced May 5, 2026
oliverlaz
added a commit
to GetStream/stream-chat-react
that referenced
this pull request
May 5, 2026
## Summary Bumps `@semantic-release/github` from 12.0.2 → 12.0.6 (and `semantic-release` 25.0.2 → 25.0.3) on master. v12.0.6 includes [semantic-release/github#1169](semantic-release/github#1169), which derives the GitHub release's `make_latest` flag from semantic-release's branch classification: - **main release branch** (`master` here) → `make_latest: "true"` (unchanged — keeps the **Latest** badge) - **maintenance branch** (e.g. `release-v13` on the v13 line) → `make_latest: "false"` Master's behavior does **not** change with this bump — it's already the main release branch and will continue claiming the Latest badge. This PR exists for parity with the v13 line (#3169) and to set a sensible floor in case a future maintenance branch is added to `.releaserc.json`.
oliverlaz
added a commit
to GetStream/stream-chat-react
that referenced
this pull request
May 5, 2026
## Summary Bumps `@semantic-release/github` from 12.0.2 → 12.0.6 (and `semantic-release` 25.0.2 → 25.0.3) so that v13 hotfixes published from `release-v13` stop overwriting the **Latest** badge on the public GitHub release pages. v12.0.6 includes [semantic-release/github#1169](semantic-release/github#1169), which sends `make_latest` on the GitHub release based on the branch type: - **main release branch** (`master` / v14 line) → `make_latest: "true"` (unchanged behavior — keeps the Latest badge) - **maintenance branch** (`release-v13`, configured with `range: "13.x"`) → `make_latest: "false"` (no longer claims the Latest badge)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It's required to not mark as latest when removing draft status after assets upload
notmark maintenance releases as latest #817make_latestproperty to the GH release POST request during publish #1157can try to create a test case later today or tomorrow.