Repository navigation
release: just release X.Y.Z and release.yml - #49
Merged
Merged
Conversation
One command, run twice around a human merge. On a main whose versions are not X.Y.Z it writes the version into plugin.json, flake.nix and every documented pin, adds a CHANGELOG heading with the commits since the last tag, and pushes chore/release-vX.Y.Z for a PR. On a main that already says X.Y.Z everywhere it tags vX.Y.Z and pushes the tag; release.yml checks the versions against the tag and publishes the GitHub release. `just quality` now fails when the versions disagree. The consumer pin-bump PRs from #47 wait on the token decision there. Part of #47. Tested: release.py --self-test; --check on main (29 locations at 0.6.0) and against 0.5.1 (fails); --dry-run of both paths in a fresh clone; ruff, actionlint, tests/self-tests.sh, docs-lint, agents-check; trial merge with #32 and #33 passes the same gates Cost: n/a (no measured figure in this cloud session) Co-Authored-By: Claude <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
2 participants
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.
Summary: releasing the devkit becomes
just release X.Y.Z, run twice around a human merge. On amainwhose versions are not X.Y.Z it bumps every version location and pusheschore/release-vX.Y.Zfor a PR; oncemainsays X.Y.Z everywhere it tags and pushesvX.Y.Z, and the newrelease.ymlpublishes the GitHub release (what Zenodo will archive, #43). Part of #47; the consumer pin-bump PRs wait on the token decision there.release.py --self-test;--checkon main (29 locations at 0.6.0) and against 0.5.1 (fails);--dry-runof both paths in a fresh clone; ruff, actionlint,tests/self-tests.sh, docs-lint, agents-check; a trial merge with #32 and #33 passes the same gatesWhat changed
scripts/release.py: bump, tag and--check. A pin is avtag in a devkit context only (marola-devkit/v…, a devkit workflow@v…,devkit-ref:, the marketplaceref, the README status line), soactions/checkout@v7and CHANGELOG history are never touched..github/workflows/release.yml: on av*tag,--checkagainst the tag, thengh release create --verify-tag --generate-notes.justfile: thereleaserecipe;qualityrunsrelease.py --check, so a PR that misses a version location fails.docs/3-development.md"Releases": the two-step flow.Try it
v0.6.0 is the first release to go through it: after this merges,
just release 0.6.0onmaintags it.Generated by Claude Code