Repository navigation
chore(release): 0.1.0 - #27
Merged
Merged
Conversation
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.
Version bump for the v0.1.0 release (minor — there are
featcommits since v0.0.3).Generated by
bun run release:prep(git-cliff):package.json:0.0.3→0.1.0(version line only — preserves Biome formatting)CHANGELOG.md: adds the[0.1.0]section rolling up everything since v0.0.3 — the Profile migration summary / estimate / external-tool signals (PR feat(profile): migration summary, duration estimate, and external-tool signals #25) and the reliable org crawl work: REST discovery, two-pass GraphQL, 502 resilience, plus repo search/pagination and thegatesscript rename (PR fix(profile): reliable org crawl (REST discovery + two-pass GraphQL) plus repo search/pagination #26).After merge
Tag
v0.1.0on the merge commit and push it — that triggersrelease.yml:guard (tag == package.json version) → 11-gate verify → build image → Trivy CRITICAL/HIGH scan → push GHCR tags → draft GitHub Release with git-cliff notes → commit the updated CHANGELOG to
main.No code changes — version + changelog only.