Repository navigation
[skip ci] Reconcile and guard locked dependency metadata - #139
Merged
Merged
Conversation
szmyty
changed the base branch from
codex/137-01-workflow-lint-20261113
to
main
November 14, 2026 01:39
szmyty
marked this pull request as ready for review
November 14, 2026 01:39
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.
Relates to #137, checkpoint 3. Stacked after #138.
Retains the existing lock byte-for-byte and makes the metadata guard explicit. Adds task ci:lock and --locked metadata resolution in the existing CI lanes; compiler/test commands that previously allowed lock mutation now retain --locked. There is no new CI trigger, job or sibling runtime dependency.
Validation: Cargo metadata refresh and a subsequent explicit-version update --workspace --locked --offline succeeded without changing the resulting lock SHA-256. All five owning lockfiles were inspected/resolved across the suite; this PR includes the owning observations in docs/work/137/03-lock-metadata.json. This does not compile products, run build scripts, tests, Clippy, native providers or hosted CI. The maintainer selected generated-source maintenance for this checkpoint; tools were installed privately for metadata/formatting only.
No Cargo manifest requirement, feature, MSRV or native authority-gate changes. Successful resolution is not proof that every locked crate compiles on the promised MSRV or that Actions is green. Locked build/conformance acceptance remains deferred and the issue stays open. [skip ci]