Repository navigation
fix(deps): update xstate tarball integrity - #20
Conversation
![kiro-systemf[bot]](https://avatars.githubusercontent.com/u/172220390?s=60&v=4){kind=small}
There was a problem hiding this comment.
Approved at exact head cda675f.
Independent ce-code-review run 20261108-190505-def2b163 is Ready to merge with no findings or testing gaps; scope and metadata match this head. Maker evidence includes sfs-deps and pnpm-store builds, frozen install, importer typecheck/lint and 13 passing tests. Effect remains unchanged.
The reviewer did not independently rebuild the source derivation or establish cross-platform reproducibility. CI check remains in progress; this approval does not waive required CI or claim full check:ci/journeys ran.
The check job's Nix pnpm-store build failed downloading the pinned pkg.alchemy.run beta.84/rc.17 tarballs with HTTP 404 (run 42512750435): upstream no longer serves those artifacts, so the offline pnpm bootstrap could not build consumer-pnpm-store. Point the three catalog pins at the stock registry versions and regenerate the lockfile. Transitive @alchemy.run/* 2.0.0-beta.85 and @distilled.cloud/* 1.0.0-rc.18 resolve from registry.npmjs.org. Effect stays at 4.1.0. Verified: no pkg.alchemy.run entry remains in the lockfile and nix develop --command pnpm bootstrap passes locally.
|
This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again. |
There was a problem hiding this comment.
Approved at 0a148ec: required check is green at this head, and I read the diff: alchemy moves from the pkg.alchemy.run tarballs (now 404) to registry 2.0.0-beta.85, the version agent-inbox already merged with. No runtime break found, and deploy is gated off (ALCHEMY_DEPLOY is not set).
SYS conductor read the diff at 0a148ec: xstate tarball integrity plus alchemy moved from 404ing pkg.alchemy.run tarballs to registry 2.0.0-beta.85; deploy job is gated off
|
@Mergifyio queue |
☑️ Command disallowed due to command restrictions in the Mergify configuration.Details
|
Summary
372be24c758e7bd08116a63d5f40ab5f9f823adfand regenerate the pnpm tarball integrity for its unchanged filename.Verification
nix build .#sfs-deps --no-link --print-out-paths -L— passed.nix build .#pnpm-store --no-link --print-out-paths -L— passed; exercises the lock against the generated tarballs.pnpm install --frozen-lockfile— passed.pnpm --filter @endgame/site typecheck— passed.pnpm --filter @endgame/site test— passed, 3 files / 13 tests.pnpm prepare && pnpm --filter @endgame/site lint— passed. Beforepnpm prepare, lint failed withUnknown plugin: 'effecttsgo'.visible + FLAG -> flagged.No new tests: this is a mechanical dependency lock update; existing importer tests exercise the behavior.
Code review: skipped (mechanical diff). Root review requested on this maker PR.
Full
pnpm check:ci(START-4) andpnpm journeys(START-5) remain pending off-host; local execution is restricted to touched-package checks (OP28).