Repository navigation
fix(relay): use released drizzle rc.5 and fail installs on unmet peers - #31016
Merged
Merged
Conversation
The relay pinned drizzle-orm and drizzle-kit to 1.0.0-rc.5-ab785fc, a
commit build that reads snapshots as `./${path}` and broke on the
absolute scratch folder alchemy beta.85 passes. The released
1.0.0-rc.5 fixes that read and is the version alchemy's peer range asks
for, so the drizzle patch goes away. rc.5 stores postgres snapshots as
a base plus diffs; the snapshots are upgraded with `drizzle-kit up`
so deploys see no schema change. Migration SQL is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ntries The relay pinned drizzle to a commit build outside alchemy's peer range, and pnpm only warned. strictPeerDependencies makes that fail whenever the lockfile is resolved, and the three existing warnings are resolved: @pierre/trees takes @pierre/theming 1.0.2, which accepts @pierre/theme 2, and the react-native-screens fork and ws 7's utf-8-validate get explicit allowances. A fresh resolve also needed @react-native/metro-config pinned to react-native's exact version. Removed entries that no longer match anything: overrides cutting edges @alchemy.run/sigil, @clerk/clerk-js and @pierre/diffs no longer declare, the expo-router override, allowBuilds for packages we no longer install, and minimumReleaseAgeExclude, whose versions have all aged past the policy (the lockfile resolves identically without it). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
ApprovabilityVerdict: Approved at Macroscope's review found this PR approvable — The change removes an obsolete Drizzle workaround and makes installs reject unmet peers, with targeted compatibility exceptions. The assessed changes do not alter product defaults or database resources, and the reported schema plan shows no change. You can add or adjust custom eligibility rules. Learn more. |
github-actions Bot
added a commit
to omarcresp/t3code-flake
that referenced
this pull request
Nov 5, 2026
**v0.1.8-nightly.20261104.4192** · 10 changes from 1 contributor **2 bug fixes.** <details> <summary>Full changelog</summary> ## What's Changed * fix(relay): use released drizzle rc.5 and fail installs on unmet peers by @juliusmarminge in pingdotgg/t3code#31016 * build: typecheck with tsrs and Effect's rules through @effect/tsgo by @juliusmarminge in pingdotgg/t3code#31028 * refactor: replace jose with effect/jose by @juliusmarminge in pingdotgg/t3code#30474 * refactor: move HMAC, key, and random work to effect/crypto by @juliusmarminge in pingdotgg/t3code#30501 * refactor(server): sign server tokens through PayloadSigner by @juliusmarminge in pingdotgg/t3code#30523 * refactor: hold relay signing keys in EnvironmentSigningKey and CloudMintSigner by @juliusmarminge in pingdotgg/t3code#30529 * refactor(client-runtime): share DPoP proof creation across web and mobile by @juliusmarminge in pingdotgg/t3code#30540 * fix(client-runtime): a thread keeps syncing after a stream defect by @juliusmarminge in pingdotgg/t3code#31071 * test(server): AgentSessionScanner blocked-repo test no longer races the git-read timeout by @juliusmarminge in pingdotgg/t3code#30554 * test(web): PDF preview tests wait on pdf.js loads and stop timing out by @juliusmarminge in pingdotgg/t3code#31104 **Full Changelog**: pingdotgg/t3code@v0.1.8-nightly.20261104.4179...v0.1.8-nightly.20261104.4192 </details> Upstream release: https://github.com/pingdotgg/t3code/releases/tag/v0.1.8-nightly.20261104.4192
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.
The relay pinned
drizzle-ormanddrizzle-kitto1.0.0-rc.5-ab785fc, a commit build from August. That build reads the migrationsoutpath as./${path}, so an absolute path broke the relay deploy and we had to patch@alchemy.run/drizzlearound it in https://git.cafe/pingdotgg/t3code/pulls/30513. The pin is also outside alchemy's1.0.0-rc.5peer range. pnpm reported that on every install, but only as a warning, so nothing failed.Drizzle
1.0.0-rc.5, which reads the path correctly, and deletes our@alchemy.run/drizzlepatch. TheArtifacts.cachedpatch stays until Artifacts.cached never settles waiters when the effect fails, hanging plan alchemy-run/alchemy#2981 is fixed.drizzle-kit up, so a deploy doesn't rewrite them on the CI runner. Migration SQL is unchanged, andDrizzle.Schemadiffs to no change.Peer rules
strictPeerDependencies: true, so resolving the lockfile fails on an unmet peer. That happens on a local install and incheck:changed's fresh resolve. With the old pin put back, resolution fails with "unmet peer drizzle-kit / drizzle-orm".@pierre/trees>@pierre/themingmoves to1.0.2, because 1.0.0 predates@pierre/theme2.allowedVersionsentries:react-native-screens: our fork is a 5.x prerelease, which>= 4.0.0excludes.utf-8-validate: it only callsisValidUTF8, which v6 doesn't change.@react-native/metro-configto0.88.0.react-native-workletspeers on any version, so a fresh resolve picks 0.88.1, while React Native's CLI wants exactly 0.88.0.Removed from
pnpm-workspace.yaml@clerk/clerk-js>@solana/*;@pierre/diffs>@shikijs/transformers.expo-routeroverride, which nothing uses.allowBuildsentries formsgpackr-extractandmsw, which we no longer install.minimumReleaseAgeExclude. pnpm adds entries but never removes them, and every listed release is now past the release-age window. The supply-chain check and a fresh resolve both pass without the list.vp run check:changedpasses, including the fresh strict resolve. 305 relay tests pass.Done by Claude Opus 5.5 in Claude Code.
🤖 Generated with Claude Code