Repository navigation
fix(release): pin cloudflare-runtime's unenv so release smoke passes strict peers - #17
Merged
Merged
Conversation
… installs pass strict peers (AI-100)
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
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.
Release Smoke started failing on
mainafter #16 (run https://github.com/AI-Escape/t3code/actions/runs/43725135491/job/132845378575). The smoke deletes the fixture lockfile and resolves fresh, andunenv 2.0.0-rc.25(published 2026-11-13) now wins@alchemy.run/cloudflare-runtime@2.0.0-beta.85'sunenv: ^2.0.0-rc.24range. That package's own@cloudflare/unenv-preset@2.16.2(still the latest) peers on exactly2.0.0-rc.24, so strict peer checks fail ininfra/relay. The committed lockfile still has rc.24, so normal installs were unaffected.Fix: a scoped override
"@alchemy.run/cloudflare-runtime>unenv": 2.0.0-rc.24next to the other drift pins, plus the matching one-line lockfile update. Strict peer checks stay on; no retries or skips.Proof:
vp install --lockfile-only --ignore-scripts:ERR_PNPM_PEER_DEP_ISSUES ... unmet peer unenv, Installed: 2.0.0-rc.25, Wanted: 2.0.0-rc.24.unenv@2.0.0-rc.24; fullnode scripts/release-smoke.ts(Node 26.12.1, jq 1.7.1 as on the runner) printsRelease smoke checks passed.vp run check:changed: all pass.Linear: AI-100
Made by Claude Opus 5.5 in T3 Code (Claude Code harness).
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.