chore: release v0.1.1#21
Closed
amcheste-ai-agent[bot] wants to merge 1 commit into
Closed
Conversation
Patch release promoting the brand-alignment + branch-model clarification + banner work that landed on develop: - docs: distinguish integration trunk from GitHub default branch setting (#19) — adds the "GitHub default branch" subsection to branching-and-releases.md and Step 5 to the release ceremony. - feat: add brand banner (#20) — Claude Design output landed under assets/, README references assets/banner.svg. - ci: bump release-drafter to v7.3.0 and drop pull_request trigger (#18, merged earlier). - ci: scorecard workflow imposter SHA + publish_results fix (merged earlier). No code changes; documentation + asset additions only. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-Authored-By: amcheste <13696614+amcheste@users.noreply.github.com>
Contributor
Author
|
Closing — this used a patch bump (0.1.1) but the release contains a Re-doing as:
|
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.
Patch release promoting the brand-alignment + branch-model clarification + banner work that landed on develop.
What's in this release
Added
assets/(svg + 1200/2400 png) perbanner-spec.md. Hero shows the four philosophy pillars with a Hunter Green δ marker on Branching.develop) is distinct from GitHub's "default branch" repo setting (develop pre-release, main post-release).mainis the GitHub default branch. Idempotent — only takes effect on the first release.#1F4D3A, version in Ink#0B0B0C) and em-dash sweep across prose.Changed
c2e2804). Dropped thepull_requesttrigger — v7 was failing CI on PR events becauseGITHUB_REFisrefs/pull/N/merge, which the Releases API rejects astarget_commitish.Fixed
github/codeql-action/upload-sarifSHA replaced with the real v4 pin. Addedpublish_resultscondition keyed todefault_branchinstead of hardcodedrefs/heads/main.Release ceremony
This PR is Step 1 of
/publish-release. Merge it, then the rest of the flow continues on CLI:git merge --no-ff origin/developinto mainv0.1.1and push the tagmainis the GitHub default branch (already is — second release on this repo, so this step is a no-op)No code changes — docs + assets only.