WIP: Migrate pinned STEVE dependency sources to the Caution forge #16
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/forge-migration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Move Bootproof and JS SDK tee-attestation-js sources to git.caution.co/public. Retain Bootproof
78f531a2c245404a9d8879fb71cc397096ae0077, tee-attestation-jsba0d0c57de673c8576c91a8730775a87575f5c10, compiler settings and container digests. Correct SDK monorepo metadata and Procfile sources, retaining EnclaveOSdda60363e43cfb00bd6b9d8bf56322bf122a5bac.Branch head versus Platform pin
Signed branch head:
d80a9a3573b6e94e57e3cbbf00745946e8f09e62. This two-parent retention merge joins5d30ca777bca0edc9fef57b42b62c1fff7eb8103and6431612db09899314c7c30bc7ca0b1c54f7bc3c0; its complete tree equals5d30ca7exactly. The SDK conflict retains the current workspace dependency declaration. No source or lockfile bytes changed in the retention merge, and the branch was pushed without rewriting history.Platform #479, revision
85e6300a99e5efb0badde6b74793746bb101e1a8, continues consuming6431612db09899314c7c30bc7ca0b1c54f7bc3c0, the migration-only descendant of original pinc0b8d2d62e66108689745561242972048f6cfce5. Platform does not adopt the newer main-based branch tree. The old pin is now reachable through the migration branch in ordinary fresh clones.Validation
6431612: JS SDK 69 passed; Rust libraries excluding the server 36 passed, 1 ignored; the pinned StageX WASM test target passed.d80a9a3: JS SDK 103 passed; Rust libraries excluding the server 56 passed, 1 ignored.upstream_idle_read_timeouts_fail_both_forwarding_paths, expectingupstream response unavailablebut receivingupstream unavailable. No unrelated runtime fix is included.6431612. These are local build checks, not live Nitro evidence.Landing gates
Keep this PR as a draft. Later merge it with a signed merge commit retaining both histories, establish GitHub synchronization from the canonical forge, then verify fresh GitHub checkout of the exact consumed STEVE and Bootproof pins before Platform lands. Mirror setup remains separate. No main-branch merge, tag, mirror configuration, deployment or trusted PCR policy change was performed.
6431612db0to5d30ca777b