Repository navigation
Conversation
A tag such as v0.1.0 now makes a GitHub release: its notes are that version's section of CHANGELOG.md, and it carries the binary built for Linux (x86_64, on Ubuntu 22.04 so that its glibc is old enough for most distributions) and macOS (Apple Silicon), with the README, the licence and the changelog. Not Windows, where nothing has been tried. A tag that is not the version Cargo.toml declares is refused, so that a binary never says one version and its release another. CHANGELOG.md starts with 0.1.0, the first version, said as vaguely as the README and as unstable. The README points to the releases, and CLAUDE.md says how a version is released. 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.
A tag such as
v0.1.0now makes a GitHub release, as cellweave does: its notes are that version's section ofCHANGELOG.md, and it carries the binary built for each platform universe is meant to run on.Each archive holds the binary, the README, the licence and the changelog. A tag that is not the version
Cargo.tomldeclares is refused before anything is made, so that a binary never says one version and its release another; a version without a section in the changelog is refused too.CHANGELOG.mdstarts with 0.1.0, the first version, as vague as the README about what is there and as insistent that it is unstable. The README points to the releases, andCLAUDE.mdsays how a version is released.Tried locally: the tag check (v0.1.0 accepted, v0.2.0 refused), the notes taken from the changelog, the YAML parsed, and
cargo build --release --locked(15 minutes on 20 cores with the fat LTO, 5.4 GB at most). The binary needs onlylibwayland-client,libffi, libc, libm and libgcc at run time, and opens the window. The workflow itself runs only on a tag, so its first real run is the release of 0.1.0, once this is merged.🤖 Generated with Claude Code