feat(release): release-check.sh conforms to repo_release_check.v1 - #11
Merged
Conversation
Adapt the existing root release-check.sh to the multi-repo preflight contract: --json emits a repo_release_check.v1 object on clean stdout (checks routed to stderr), exit 0; --json/--dry-run skip the clean-git-tree check (preflight owns it). Human mode unchanged. Existing checks preserved (VERSION/pyproject/ CHANGELOG surfaces, docs presence, pytest, CLI, compileall, MCP payloads, no weights/.env). Verified: shellcheck clean; --dry-run --json emits valid READY JSON against the real venv; human --dry-run exits 0. Co-Authored-By: Claude Opus 4.8 <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.
Release-check rollout for mq-agent's multi-repo preflight (contract: mq-agent
docs/STACK_RELEASE_ALL_EXECUTE.md). mq-image-analyze's rootrelease-check.shemitted human text, so preflight reportedinvalid JSON.--json→repo_release_check.v1on clean stdout, exit 0 (status carries the verdict);--json/--dry-runskip the clean-tree check (preflight owns it).Verified: shellcheck clean;
--dry-run --json→ valid READY JSON against the real venv; human mode exit 0. Read-only; no release/tags.