Make CLI release idempotent#289
Conversation
|
Caution Review failedPull request was closed or merged during review 📝 WalkthroughWalkthroughThese changes modify the release process configuration: the CI workflow now force-updates git tags during repeated releases, whilst GoReleaser is configured to replace existing releases rather than follow default handling. Changes
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
|
Updates to Preview Branch (work/confident-cannon) ↗︎
Tasks are run on every commit but only new migration files are pushed.
View logs for this Workflow Run ↗︎. |
🏷️ Release PreviewWhen this PR is merged, it will automatically create:
The changelog will be updated and committed automatically. 💡 Tip: Update the changelog heading to control release type:
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
🐝 Review App Deployed Homepage: https://hover-pr-289.fly.dev |
Summary
git tag -f) so reruns don't fail on existing tagsrelease.mode: replaceto goreleaser so it updates existing GitHub releasesFixes the
cli-v0.1.0release which passed goreleaser but failed at npm publish, then couldn't be retriggered.Test plan
cli-v0.1.0, confirm Release CLI workflow passes through to npm publishSummary by CodeRabbit
Release Notes