Repository navigation
fix(release): ship self-contained managed Prime archives - #60
Merged
Merged
Conversation
34 of 51 tasks
8 of 16 tasks
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
1 participant
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.
Managed preview installation extracted a root archive that could not start: its CLI required
undiciand other runtime packages that were absent. The prior smoke test masked this by running npm install.Recipe 2 packs the full committed runtime dependency graph into the signed root archive. Build-input acquisition downloads only lockfile URLs and verifies SHA-512; offline packing revalidates those bytes, preserves nested dependencies, peers and all platform optionals, and copies the exact built workspace archives. Installation and current-recipe smoke invoke no npm install or lifecycle scripts. The smoke loads CLI, SDK and native/WASM dependencies directly and retains the owned daemon cleanup proof. Packing resolves the physical staging path so npm retains bundles beneath symlinked temporary directories.
Policy 4 registers the changed preview/stable workflows while preserving historical recipes and policies. Pylon companion #487 is merged and accepts the recipe and bounded per-file PAX metadata used by long dependency paths.
Validation: 205 publication tests passed with zero skips; 22 focused release tests passed, including a real archive regression that failed before the physical-path fix. Required npm check and normal commit hooks passed. Checkpoint adversarial review passed with scoped corrections. Clean-source recipe 2 build/pack, all 196 bundled dependency-manifest checks, and macOS installed CLI/SDK/native-module/owned-daemon smoke passed at 69c6b74 (tree fe3ecef9c5e59b5ef639e046f2cf7644cbe5fe16). The root archive is 43,135,559 bytes. The first hosted run passed both isolated offline packs, byte reproducibility, installed runtime checks on both OSes, all ordinary tests and 205 publication cases on each OS. macOS stress exposed an existing unrecognized safe losing-builder refusal. A captured three-process regression now proves native open loss after valid peer cleanup, unchanged winning checkpoint/inode, zero callbacks and fresh recovery; only that exact migration refusal is accepted. The corrected full stress suite passed 29/29 locally with zero skips, and its scoped review passed. The first run was cancelled after preserving its failure and partial Linux crash evidence. Fresh CI must pass all current tests, 3,034 crash cuts and actual 16 MiB limits on both OSes before merge. Signed publication and protected Pylon artifact graduation remain required after merge before stable promotion.
The existing immutable recipe 1 preview is retained as historical evidence and will not be promoted.
Model: GPT-6. Harness: Codex in Pylon.