Repository navigation
ci(release): cut a release automatically on every merge to main - #18
Merged
Merged
Conversation
Releases only happened when someone remembered to push a tag, so merged features (the version display, upload types, the CLI) sat on main for weeks without reaching the deployed image. - `auto-release.yml` runs on every push to main and asks `scripts/prepare-release.ts` what to do: an untagged prepared version is released as-is; a feat/fix/perf/revert PR bumps the patch (minor for `!`) and moves the Unreleased changelog notes under a dated heading; anything else is skipped. - `release.yml` is also a reusable workflow taking the tag, since a tag pushed with GITHUB_TOKEN never triggers it. Manual tag pushes still work. - The 0.0.24 changelog now covers the PRs merged after it was written; it ships as the first automatic release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Caution Review failedThe pull request is closed.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. CodeRabbit Verify
|
flyingwebie
marked this pull request as ready for review
November 3, 2026 13:43
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.
What changed
.github/workflows/auto-release.yml(new) runs on every push tomainand callsscripts/prepare-release.tsto decide:package.jsonversion has nov<version>tag (a hand-prepared release) → release it as-isfeat/fix/perf/revert→ bump the patch (minor for!), move## Unreleasedchangelog notes under a dated heading (or use the PR title), commitchore(release): <version>, tag, releasedocs,chore,test,refactor, upstream syncs) → no releaserelease.ymlis now also a reusable workflow taking ataginput, because a tag pushed withGITHUB_TOKENnever triggers it. Manual tag pushes still work.CHANGELOG.md: the 0.0.24 notes now cover the PRs merged after it was prepared (version display, upload types, CLI, MCP fixes).docs/deployment/release-workflow.mddescribes the new flow.Why
Releases only happened when someone pushed a tag. Features merged since Oct 6 (including the running-version display) never reached the deployed image. The last release was v0.0.22.
Impact
ghcr.io/flyingwebie/instatic:<version>and:latest, plus the GitHub Release.:latestwith auto-update.Verification
bun test scripts/prepare-release.test.ts: 9 passbun run build,bun test(7678 pass, 0 fail) andbun run lintall pass🤖 Generated with Claude Code