chore: bump @semantic-release/github to ^12.0.6#3169
Merged
oliverlaz merged 2 commits intorelease-v13from May 5, 2026
Merged
Conversation
Picks up semantic-release/github#1169, which sets make_latest=false on GitHub releases for non-main release branches. v13 hotfixes published from release-v13 will no longer be flagged as "Latest" on the public GitHub release pages, leaving the badge on the master/v14 line. Also bumps semantic-release ^25.0.2 -> ^25.0.3.
MartinCupela
approved these changes
May 5, 2026
After deduping the lockfile, @types/react@* (transitive via @types/react-image-gallery) folded into the direct ^19.0.7 entry. React 19's types removed the global JSX namespace, so use React.JSX.IntrinsicElements instead. The @ts-expect-error in ModalGallery existed to suppress the @types/react 18<->19 mismatch with react-image-gallery; with both on 19, the suppression is unused.
oliverlaz
added a commit
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`.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release-v13 #3169 +/- ##
===============================================
- Coverage 80.93% 80.92% -0.01%
===============================================
Files 506 506
Lines 10563 10563
Branches 2482 2482
===============================================
- Hits 8549 8548 -1
- Misses 1580 1581 +1
Partials 434 434 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
Summary
Bumps
@semantic-release/githubfrom 12.0.2 → 12.0.6 (andsemantic-release25.0.2 → 25.0.3) so that v13 hotfixes published fromrelease-v13stop overwriting the Latest badge on the public GitHub release pages.v12.0.6 includes semantic-release/github#1169, which sends
make_lateston the GitHub release based on the branch type:master/ v14 line) →make_latest: "true"(unchanged behavior — keeps the Latest badge)release-v13, configured withrange: "13.x") →make_latest: "false"(no longer claims the Latest badge)