Repository navigation
ci: migrate releases from semantic-release to release-it - #683
Merged
Merged
Conversation
Releases still run automatically on every push to master:
- Only when there is a feat, fix, perf or breaking-change commit since
the last tag, as with semantic-release. release-it on its own would
cut a patch release for chore/ci commits too.
- Version bump and release notes come from the commits via
@release-it/conventional-changelog (angular preset, same as before).
- Same tag (v${version}) and release commit message
("chore(release): ${version} [skip ci]") as before.
- npm publish uses trusted publishing (OIDC) instead of NPM_TOKEN,
which had expired (E401). The GitHub release and the push use the
built-in GITHUB_TOKEN instead of the GH_TOKEN PAT.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Replaces semantic-release with release-it. Releases still happen automatically on every push to
master.What stays the same
feat,fix,perfor breaking-change commit since the last tag. release-it on its own would also cut a patch forchore:/ci:commits, so a step inpublish.ymlskips those pushes.@release-it/conventional-changelog, angular preset, same as semantic-release's default).v${version}, and the release commit is stillchore(release): ${version} [skip ci].CHANGELOG.md; notes go to the GitHub release.What changes
NPM_TOKENsecret (expired: E401 on every run since #680)GH_TOKENPATGITHUB_TOKEN(contents: write)concurrencygroupnpm.skipChecksis on because release-it'snpm whoamicheck doesn't work with OIDC.Before merging
@react-native-picker/picker→ Settings → Trusted Publisher, then add GitHub Actions with repositoryreact-native-picker/pickerand workflowpublish.yml. Without it, the publish step fails.NPM_TOKENandGH_TOKENsecrets can be deleted.Testing
release-it --ci --dry-runlocally: 2.11.4 → 2.11.5, notes list fix(ci): repair Android, iOS and macOS example builds #680, thennpm publish --dry-run, commit, tag and push in the expected order.release=trueforv2.11.4..HEAD(hasfix(ci):from fix(ci): repair Android, iOS and macOS example builds #680), andfalsefor ranges with onlyci:/chore:commits.Merging this triggers the first release, 2.11.5. It includes #680–#682. The only published-code change in those is #682's Flow type annotations in
js/, which don't change runtime behaviour.🤖 Generated with Claude Code