ci: automate releases with release-please and enforce conventional commit titles - #14
Open
ChocoStout wants to merge 1 commit into
Open
ChocoStout wants to merge 1 commit into
ChocoStout wants to merge 1 commit into
Conversation
…mmit titles Replace the manual `v*`-tag release flow with trunk-based automation: merging Conventional Commits to `main` maintains a release PR; merging that PR publishes both packages to NuGet.org + GitHub Packages and cuts the GitHub Release. Release automation: - release.yml: release-please job + gated publish job (build -> test -> pack -> push -> attach assets) - release-please-config.json + .release-please-manifest.json (manifest mode, baseline 1.1.0, tags stay vX.Y.Z via include-component-in-tag:false) - Directory.Build.props: <VersionPrefix> annotated x-release-please-version - CHANGELOG.md: relabel stale [Unreleased] -> [1.1.0] (already shipped) Conventional Commits enforcement + docs: - pr-title-lint.yml: validate PR titles (amannn/action-semantic-pull-request@v6) - pull_request_template.md: title reminder + checklist - CONTRIBUTING.md: new "Commit messages" section + rewritten "Releasing" - README.md: contributing step asks for a Conventional Commits title Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
1 participant
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
Migrates OverTone to automated, trunk-based releases via release-please, replacing the manual
v*-tag flow. Merging Conventional Commits tomainmaintains a "release PR"; merging that PR publishes both packages to NuGet.org + GitHub Packages and cuts the GitHub Release.Changes
Release automation
release.yml→release-pleasejob + gatedpublishjob (build → test → pack → push → attach.nupkg/.snupkg)release-please-config.json+.release-please-manifest.json— manifest mode, baseline1.1.0, tags stayvX.Y.Z(include-component-in-tag: false)Directory.Build.props—<VersionPrefix>annotatedx-release-please-version(now machine-managed)CHANGELOG.md— relabeled stale[Unreleased]→[1.1.0](those features already shipped)Conventional Commits enforcement + docs
.github/workflows/pr-title-lint.yml— validates PR titles viaamannn/action-semantic-pull-request@v6.github/pull_request_template.md— title reminder + checklistCONTRIBUTING.md— new "Commit messages" section + rewritten "Releasing"README.md— contributing step asks for a Conventional Commits titleFollow-ups (repo settings — not code, intentionally out of this PR)
NUGET_API_KEYrepo secret for NuGet.org (GitHub Packages uses the built-in token)squash_merge_commit_title=PR_TITLEso the enforced PR title is what release-please reads (repo currently merge-commits)mainlast-release-shafromrelease-please-config.jsonafter the first release-please releaseNotes
ci:-typed, so merging it won't trigger a release — release-please only acts onfeat/fix.pr-title-lintdoesn't run on this PR (not onmainyet); it applies to subsequent PRs.🤖 Generated with Claude Code