Skip to content

ci: migrate releases from semantic-release to release-it - #683

Merged
Naturalclar merged 1 commit into
masterfrom
ci/release-it
Nov 18, 2026
Merged

Naturalclar merged 1 commit into
masterfrom
ci/release-it

Conversation

@Naturalclar

Copy link
Copy Markdown
Contributor

Replaces semantic-release with release-it. Releases still happen automatically on every push to master.

What stays the same

  • Releases only happen when there's a feat, fix, perf or breaking-change commit since the last tag. release-it on its own would also cut a patch for chore:/ci: commits, so a step in publish.yml skips those pushes.
  • Versions and release notes come from conventional commits (@release-it/conventional-changelog, angular preset, same as semantic-release's default).
  • Tags are still v${version}, and the release commit is still chore(release): ${version} [skip ci].
  • Still no CHANGELOG.md; notes go to the GitHub release.

What changes

Before After
npm auth NPM_TOKEN secret (expired: E401 on every run since #680) npm trusted publishing (OIDC), no token
GitHub release + push GH_TOKEN PAT built-in GITHUB_TOKEN (contents: write)
Node 22 24, with npm updated to latest (trusted publishing needs npm ≥ 11.5.1)
Concurrent pushes could race queued with a concurrency group

npm.skipChecks is on because release-it's npm whoami check doesn't work with OIDC.

Before merging

  • Configure trusted publishing on npm. On npmjs.com, open @react-native-picker/picker → Settings → Trusted Publisher, then add GitHub Actions with repository react-native-picker/picker and workflow publish.yml. Without it, the publish step fails.
  • After that, the NPM_TOKEN and GH_TOKEN secrets can be deleted.

Testing

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

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>
@Naturalclar
Naturalclar merged commit b4d5c83 into master Nov 18, 2026
@Naturalclar
Naturalclar deleted the ci/release-it branch November 18, 2026 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant