Repository navigation
Describe main as v0.8.0 without the pre-release - #280
Merged
Merged
Conversation
The README drops the note on the published pre-release crates and the instruction to depend on main, and AGENTS.md's project status describes the tree as v0.8.0, with pre-release versions treated as test runs that no document names. 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
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.
This PR makes
cgp's README andAGENTS.mddescribe themainbranch as the v0.8.0 release, asthough v0.8.0 had already shipped. It removes every note about the pre-release crates published on
the way to v0.8.0. That brings the repository in line with the knowledge base's
rule on versions,
which the knowledge base, the
/cgpskill, andcargo-cgp's README already follow. The changeedits documentation in two files and leaves code, tests, and snapshots untouched.
The edits are correct under that rule. But until v0.8.0 and
cargo-cgpv0.1.0 are published, theREADME's install commands give a reader the wrong versions, so this PR should merge with those
releases. Merge timing explains why.
What changes
README
The README now addresses a reader of v0.8.0 and stops explaining how to reach v0.8.0 before its
release. It changes in these places:
v0.7.0, and where the v0.7.0 documentation lives. It drops the statement that
maintracks anupcoming release published as pre-release crates.
cargo add cgpinstalls v0.7.0 and told thereader to depend on
mainthrough a git dependency until v0.8.0 shipped. The section now endswith
cargo add cgpand the prelude import.cargo-cgpparagraph: pins thenix runflake reference to thev0.1.0tag and calls thetool "an early release" instead of a pre-release.
is young and still evolving.
AGENTS.md
The project-status section now states the documentation rule for agents directly. The tree is
v0.8.0, and its manifests may carry a pre-release suffix while the release process is tested. Every
document, comment, and README describes the tree as v0.8.0 and never names that suffix. The section
links the knowledge-base rule and applies it to every sibling crate, including
cargo-cgpv0.1.0.Two smaller edits follow from that rule. The v0.7.0 paragraph calls v0.7.0 "the previous official
release" instead of "the stable release on crates.io". The workspace-versioning convention names
the lockstep version as 0.8.0 instead of quoting the manifests' current suffix.