public/locksmith
6
0
Fork 0
Code Issues 3 Pull requests 1 Activity

WIP: Migrate dependency sources to the Caution forge #18

Closed
vincent wants to merge 0 commits from feat/forge-migration into main
pull from: feat/forge-migration
merge into: public:main
Conversation 1 Commits - Files changed -
vincent commented 2026-10-15 11:55:28 +00:00
Owner
Copy link

Current branch refresh

Signed head: 41daa57cacdf5088259e64da683c429396c9d191. Merged current Locksmith main (cfc39f2fd8c395d65eeacbe7b777ab6f3e5027c1) into this existing PR branch with an ancestry-preserving merge; no force-push. The resulting source tree is byte-identical to previous head b9100df30490f5a3983705e36a277c82860c0207.

The only pinned Git dependency here is Bootproof (both bootproof and bootproof-sdk). Its existing 2590edb0f23cae6589bc73cc8324673023ac1deb pin is already the latest feat/historical-proof-verification head and contains fixes not on Bootproof main. Retained it rather than downgrading to the older default branch. Dependency versions, image digests, and Cargo.lock are unchanged. Platform/STEVE pins and dev01 were not modified.

Fresh validation

Native Linux, Rust/Cargo 1.93.0, isolated Cargo home and target directory. A test-only Cargo source replacement redirects the historical Distrust registry to sparse+https://git.caution.co/api/packages/public/cargo/. All 14 recovered crate archives match the locked checksums. No inherited Git aliases or existing Cargo cache were used for the initial fetch.

  • cargo fetch --locked — passed.
  • cargo test -p locksmith -p public-cert-service --locked --offline — passed.
  • cargo test -p keymaker --locked --offline --no-default-features — passed.
  • cargo test -p locksmith -p public-cert-service --locked --offline --features locksmith/unsafe-e2e,public-cert-service/unsafe-e2e — passed.
  • cargo test -p keymaker --locked --offline --no-default-features --features unsafe-e2e — passed.
  • cargo check --workspace --all-targets --locked --offline — passed.
  • cargo test --workspace --lib --locked --offline --no-default-features — passed.

The registry replacement is not committed by this refresh. The old registry configuration remains a separate build blocker; these successful tests do not prove the unmodified container can fetch dependencies. No new container/EIF build or deployment was performed. The PR remains a draft.

Previous migration work and validation

Move Bootproof dependency fetches and deployment app_sources to git.caution.co/public, retaining Bootproof 2590edb0f23cae6589bc73cc8324673023ac1deb. The certificate-service recipe retries locked fetches through GitHub using command-scoped transport aliases for both canonical Caution and historical Codeberg URLs. Compiler settings, container digests and private registry references remain unchanged.

Previously validated branch head: b9100df30490f5a3983705e36a277c82860c0207. Platform #479 deliberately continues consuming ancestor eee2a8a3673c92b668b0a82d0da2e06c131df6e2. The branch retains the workspace dependency deduplication and verified issue-link cleanup; the stabilization commit restores the historical transport alias without changing Cargo.lock.

Validation at that previous branch head: 88 workspace library tests passed, 3 ignored. Clean-cache locked Cargo resolution and offline metadata passed in the pinned StageX environment after a native crates.io timeout. The resolved graph has no duplicate Git identities or active legacy Caution Git sources; the private registry remains an explicit exclusion. Forced-primary-failure runs of the actual retry command passed for both current and historical Codeberg dependency sources, with unchanged locks. Signatures, exact source archives and fresh canonical clone/checkout of Platform’s consumed pin were verified.

The final Platform revision 85e6300a99e5efb0badde6b74793746bb101e1a8 also passed a fresh EIF build containing Locksmith eee2a8a; this is local build evidence, not live Nitro or secret-release evidence.

Keep this PR as a draft. Landing requires a signed ancestry-preserving merge, configured GitHub synchronization, and fresh GitHub checkout of the exact consumed Locksmith and Bootproof pins. Durable retention of branch-only Bootproof 2590edb is a separate prerequisite. No main-branch merge, tag, mirror configuration, deployment or trusted PCR policy change was performed.

## Current branch refresh Signed head: `41daa57cacdf5088259e64da683c429396c9d191`. Merged current Locksmith `main` (`cfc39f2fd8c395d65eeacbe7b777ab6f3e5027c1`) into this existing PR branch with an ancestry-preserving merge; no force-push. The resulting source tree is byte-identical to previous head `b9100df30490f5a3983705e36a277c82860c0207`. The only pinned Git dependency here is Bootproof (both `bootproof` and `bootproof-sdk`). Its existing `2590edb0f23cae6589bc73cc8324673023ac1deb` pin is already the latest `feat/historical-proof-verification` head and contains fixes not on Bootproof `main`. Retained it rather than downgrading to the older default branch. Dependency versions, image digests, and Cargo.lock are unchanged. Platform/STEVE pins and dev01 were not modified. ### Fresh validation Native Linux, Rust/Cargo 1.93.0, isolated Cargo home and target directory. A test-only Cargo source replacement redirects the historical Distrust registry to `sparse+https://git.caution.co/api/packages/public/cargo/`. All 14 recovered crate archives match the locked checksums. No inherited Git aliases or existing Cargo cache were used for the initial fetch. - `cargo fetch --locked` — passed. - `cargo test -p locksmith -p public-cert-service --locked --offline` — passed. - `cargo test -p keymaker --locked --offline --no-default-features` — passed. - `cargo test -p locksmith -p public-cert-service --locked --offline --features locksmith/unsafe-e2e,public-cert-service/unsafe-e2e` — passed. - `cargo test -p keymaker --locked --offline --no-default-features --features unsafe-e2e` — passed. - `cargo check --workspace --all-targets --locked --offline` — passed. - `cargo test --workspace --lib --locked --offline --no-default-features` — passed. **The registry replacement is not committed by this refresh.** The old registry configuration remains a separate build blocker; these successful tests do not prove the unmodified container can fetch dependencies. No new container/EIF build or deployment was performed. The PR remains a draft. ## Previous migration work and validation Move Bootproof dependency fetches and deployment app_sources to git.caution.co/public, retaining Bootproof `2590edb0f23cae6589bc73cc8324673023ac1deb`. The certificate-service recipe retries locked fetches through GitHub using command-scoped transport aliases for both canonical Caution and historical Codeberg URLs. Compiler settings, container digests and private registry references remain unchanged. Previously validated branch head: `b9100df30490f5a3983705e36a277c82860c0207`. [Platform #479](https://git.caution.co/public/platform/pulls/479) deliberately continues consuming ancestor `eee2a8a3673c92b668b0a82d0da2e06c131df6e2`. The branch retains the workspace dependency deduplication and verified issue-link cleanup; the stabilization commit restores the historical transport alias without changing Cargo.lock. Validation at that previous branch head: 88 workspace library tests passed, 3 ignored. Clean-cache locked Cargo resolution and offline metadata passed in the pinned StageX environment after a native crates.io timeout. The resolved graph has no duplicate Git identities or active legacy Caution Git sources; the private registry remains an explicit exclusion. Forced-primary-failure runs of the actual retry command passed for both current and historical Codeberg dependency sources, with unchanged locks. Signatures, exact source archives and fresh canonical clone/checkout of Platform’s consumed pin were verified. The final Platform revision `85e6300a99e5efb0badde6b74793746bb101e1a8` also passed a fresh EIF build containing Locksmith `eee2a8a`; this is local build evidence, not live Nitro or secret-release evidence. Keep this PR as a draft. Landing requires a signed ancestry-preserving merge, configured GitHub synchronization, and fresh GitHub checkout of the exact consumed Locksmith and Bootproof pins. Durable retention of branch-only Bootproof `2590edb` is a separate prerequisite. No main-branch merge, tag, mirror configuration, deployment or trusted PCR policy change was performed.
Repoint issue links, drop the unused Codeberg fetch alias and declare
bootproof once in the workspace. Locked revisions are unchanged.
Retain command-scoped GitHub transport aliases for canonical Caution and historical Codeberg sources, without changing locked revisions or compiler settings.
Bring PR #18 up to date with cfc39f2 while preserving all existing migration commits. Bootproof and bootproof-sdk already pin the latest historical-proof-verification revision, 2590edb; retain those security fixes. No source-tree, dependency-version, lockfile, or image-digest changes.
anton force-pushed feat/forge-migration from 41daa57cac to b9100df304 2026-10-19 19:05:30 +00:00 Compare
anton commented 2026-10-19 19:07:33 +00:00
Owner
Copy link

Merged via CLI

Merged via CLI
anton closed this pull request 2026-10-19 19:07:33 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
public/locksmith!18
No description provided.