Repository navigation
ci: release through release-tools; version: 0.2.0 in the bundle manifest - #12
Merged
Merged
Conversation
Archetype releases were cut by hand with gh release create, so they got no themed notes and no Discord post. This adds the thin Release caller for release-tools' plugin-release.yml@v2, which reads version: from protoagent.bundle.yaml and labels the release as an archetype. It also adds version: 0.2.0, the current latest tag (v0.2.0). There are no unreleased changes since v0.2.0, so this cuts no release. protoAgent's bundle loader ignores the key. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
![protoreview[bot]](https://avatars.githubusercontent.com/in/4233969?s=60&v=4){kind=small}
There was a problem hiding this comment.
QA panel review — PASS
code-review-structural · head 6425eb4f9638 · formal
No findings were raised, so there was nothing to verify. The panel reviewed both files in full across all lanes and found no defects. The change is a thin-caller release workflow plus a single additive version key in the bundle manifest — low risk, no disagreements, no coverage gaps.
No findings — the review came back clean.
findings JSON (machine-readable)
[]
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.
Onboards this archetype onto the fleet release path (release-tools
plugin-release.yml@v2, which auto-detectsprotoagent.bundle.yamlas an archetype).protoagent.bundle.yaml: top-levelversion: 0.2.0, equal to the current latest tagv0.2.0.compare v0.2.0...mainis empty, so no release is cut. protoAgent'sload_bundleignores the key. The installer's update check still reads semver tags, so the tag remains the version of record..github/workflows/release.yml: the thin caller, with the fork guard namingprotoLabsAI/cowork-archetype. It fires on achore: release vX.Y.Zsquash subject on main or ongh workflow run Release. This PR's subject isci:, so merging it does not fire.Note: tag
v0.2.0exists but has no GitHub release page (an orphan from hand-cutting). Once release-tools v2.7.0 is out,gh workflow run Releaseon this repo creates that release page.From now on, bump
version:in the release PR and merge it aschore: release vX.Y.Z. Nevergh release createby hand.🤖 Generated with Claude Code