Repository navigation
CLAUDE.md: a release is tagged where it lands on main - #30
Merged
Merged
Conversation
Lumen is now consumed by tag (v0.8.0 is the first), and nothing said how a release becomes one. Writes down the practice the 0.8.0 tag followed: version bumped by the releasing PR's last commit, an annotated tag on the commit where the release lands on main, pushed by name, never moved. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Lumen got its first tag today:
v0.8.0, annotated, onedf6a5a— the merge of #29, which completed 0.8.0 together with #28. Downstream projects can now pinlumen @ git+https://github.com/latticedynamics/lumen.git@v0.8.0instead of a path, so a result names the exact Lumen that produced it.Nothing in
CLAUDE.mdsaid how a release becomes a tag, so the next version bump wouldn't get one. This adds a Releases section that writes down the practice the 0.8.0 tag followed. It doesn't invent a new one.What it says
0.8.0 — ….main, not the commit where the version was typed. 0.8.0 shows why they differ: the bump was written onfeat/sdm-donate, state: a state returned by forward holds only itself #28 merged tomainin between, and the release is the merge that contains both.git pushdoesn't send tags.Versions before 0.8.0 stay untagged unless one is needed. The section says how to tag them retroactively.
Docs only. No code or test changes.
🤖 Generated with Claude Code