Repository navigation
chore: prepare qualified component release 0.0.95 - #211
Merged
Merged
Conversation
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.
Prepare installation-component version 0.0.95 from qualified main
dfc3dd5db8f9fe913b3eeaa1a8099cf91c661ff0after source qualification #210. That increment passed all 27 final-head checks, and main CI/security passed. This PR changes only Cargo.toml and Cargo.lock: the workspace package, three local dependency declarations and four local package versions. External dependencies, registry checksums, toolchains, kit identity, profile declarations, workflows, runner bindings and credentials are unchanged.Final preparation head:
9c64b2d03d1e15fbc71a4471bd9f47743e1e5b64. Source-only TOML validation proved every registry package record unchanged and exactly four local package-version updates. Exact-head CI and security passed. All 27 attached checks are accepted, including all three OS tests, MSRV, static/supply-chain/import boundaries and standalone-package verification.Part of the seven-component family increment under ai-stp #1073. GitHub/PyPI/crates.io were rechecked at 2026-10-26T05:55Z: current public release 0.0.94; 0.0.95 unused in every channel for all seven components. The changelog remains Unreleased until an actual release exists; no future release-ledger heading is invented.
After exact-head and main qualification, publish this component's immutable 0.0.95 tag through the existing release/crates/PyPI workflows and verify six OS/architecture assets, checksums and provenance. Do not update ai-stp's family pin/routes until all seven authenticated component journeys pass. Retained plans keep exact old release identities. This does not close wider MCP/content/collision/vendor-loading/platform acceptance.
No tag/release/workflow publication was triggered by this PR. No local component build/runtime or package generation, new cache/clone/worktree, vendor executable change, L2 setup, user snapshot or host/agent restart. No public ai-stp CLI/Desktop release/tag. Before tagging, rollback is closing/reverting this preparation; after publication use an immutable corrective follow-up release.