Skip to content

fix(msgs): prepare 2.1.0 and reject missing release tags - #4

Merged
mrgh97 merged 1 commit into
PhyAgentOS:masterfrom
mrgh97:fix/msgs-2.1.0-release
Nov 12, 2026
Merged

mrgh97 merged 1 commit into
PhyAgentOS:masterfrom
mrgh97:fix/msgs-2.1.0-release

Conversation

@mrgh97

@mrgh97 mrgh97 commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

Manual PyPI run 43168818885 failed during checkout because forge-msgs-v2.0.1 did not exist; it never reached package upload. Selecting a tag name in Run workflow does not create one.

Prepare the requested Msgs 2.1.0 family release (forge-msgs-v2.1.0), synchronizing Python/Rust/C++ versions and the two locks. Keep Pillow >=13,<14, the v1 Arrow interface and other package-family versions unchanged. Check that release tags exist and are annotated before checkout, with regression coverage for missing/lightweight/valid tags. Update both README languages and correct the Trusted Publisher owner to PhyAgentOS in the release guide.

Validation:

  • Python: 923 passed, including three executions of the actual resolver shell against tag API outcomes; Ruff/schema/version gate passed.
  • Rust: 137 passed; both workspace crates packaged and verified.
  • Msgs 2.1.0 wheel and sdist built and validated from a clean commit; SHA256SUMS generated.
  • Actual candidate-wheel environment reports Msgs 2.1.0 / Pillow 13.0.0 / Dora 1.0.1. Standalone Gateway dora run (10s) and image/depth/state chain containing adapter-forge-gateway (10s) passed with exit 0 and HTTP/WebSocket assertions. This is a small synthetic smoke test, not hardware, sustained-run or the previously failing 640x480 multi-consumer acceptance.
  • C++ validation is performed by the PR's Linux CI.

After CI and review, merge the fix and create an annotated forge-msgs-v2.1.0 tag at that exact merged release commit. No package upload or GitLab synchronization has happened as part of this PR.

@mrgh97
mrgh97 merged commit 87a9bba into PhyAgentOS:master Nov 12, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant