Repository navigation
fix(release): qualify component tags correctly - #57
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
DamianReeves
force-pushed
the
fix/qualify-core-cli-metadata
branch
from
October 28, 2026 20:56
7ea0c6d to
b0e4752
Compare
Core wheel metadata changed after 0.1.0 publication. Prepare core 0.1.1 and CLI 0.1.2 without weakening the published-core byte guard or moving python-v0.1.1.
DamianReeves
force-pushed
the
fix/qualify-core-cli-metadata
branch
from
October 28, 2026 21:00
b0e4752 to
8016fa6
Compare
DamianReeves
changed the title
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.
Two tag-only release paths failed before publication. CLI 0.1.1 correctly refused a rebuilt core 0.1.0 wheel whose documentation metadata differs from PyPI. The extension 0.5.0 run correctly refused its extension tag when the workflow forwarded it to the native-wheel verifier.
Prepare core 0.1.1 and CLI 0.1.2 with consistent version constants, tests, lockfile and CLI README. Route extension/manual native-wheel verification through the source native version while retaining strict validation of explicit native tags. Keep all candidate-set checks and the published-core byte guard. No compiler or protocol behavior changes.
Validation: an actual workflow-shell regression reproduces the extension-tag failure before the fix, then passes manual, native, extension and invalid-native routes. The candidate tests report 22 passed and one intentional skip; actionlint passes. Full local checks pass with the verified published native 0.1.2 wheel, including 2,637 tests, 34 BDD scenarios, lint, formatting and strict type checks.
Refresh the committed host-evidence fallback, which selective documentation CI correctly rejected after earlier documentation input changes. Actual qualification from a clean source snapshot passes the pinned Rust-host recipe, offline round trips and both MoonBit refusal probes. A regression now checks the real fallback against its documented inputs.
The existing OpenSpec change records these blockers. Native 0.1.2 remains published at its original source. Preserve the failed python-v0.1.1 tag. Corrected core/CLI tags and retargeting the still-unpublished extension 0.5.0 tag require approval for the reviewed source before repeating release qualification; no released tag will move.
Tracked by morphir-5hxy.6, morphir-5hxy.7 and morphir-5hxy.8.