Skip to content

chore: migrate from release-please to semantic-release#1024

Open
scottlovegrove wants to merge 2 commits intomainfrom
scottl/semantic-release
Open

chore: migrate from release-please to semantic-release#1024
scottlovegrove wants to merge 2 commits intomainfrom
scottl/semantic-release

Conversation

@scottlovegrove
Copy link
Copy Markdown
Contributor

@scottlovegrove scottlovegrove commented Mar 29, 2026

Summary

  • Replace release-please with semantic-release for automated versioning, changelog generation, and npm publishing
  • Based on doist/typist reference implementation, simplified: no next branch
  • GitHub Packages publishing preserved
  • Storybook deployment preserved — deploy-storybook.yml triggers on v* tags which semantic-release creates automatically
  • Add prepublishOnly script to safeguard against broken publishes

Changes

  • Created: release.config.js, .github/workflows/release.yml
  • Modified: package.json (added semantic-release devDeps, publishConfig.provenance, prepublishOnly), .eslintignore
  • Deleted: .github/workflows/release-please.yml, .github/workflows/publish.yml, .github/release-please-config.json, .github/release-please-manifest.json

Pre-merge checklist

  • Update npm trusted publisher config to reference .github/workflows/release.yml
  • Add doistbot app as bypass actor on the main branch ruleset

Test plan

  • After merge, verify the release.yml workflow runs and exits cleanly (no release expected from a chore: commit)
  • On next feat:/fix: merge, verify: GitHub release created, npm package published to both npm and GitHub Packages, CHANGELOG.md updated, package.json version bumped
  • Verify storybook deployment triggers on the new release tag

Part of https://github.com/Doist/todoist-web/issues/16941

🤖 Generated with Claude Code

Replace release-please with semantic-release for automated releases,
using doist/typist as the reference implementation (simplified: no
`next` branch, no GitHub Packages dual publishing).

Add prepublishOnly script to safeguard against broken publishes.
Storybook deployment continues to work via v* tag trigger.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@scottlovegrove scottlovegrove self-assigned this Mar 29, 2026
After semantic-release publishes to npm, reconfigure for the GitHub
Packages registry and publish there too (matching the old publish.yml).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown

@doistbot-app doistbot-app bot left a comment

Choose a reason for hiding this comment

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

Thank you for migrating the repository's automated versioning and publishing system from release-please to semantic-release. The changes cleanly simplify the release pipeline while preserving essential workflows like Storybook deployments and adding helpful publish safeguards. No issues were flagged during the review.

Share FeedbackReview Logs

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