chore(deps): grafast 1.1.2, postgraphile 5.1.4 - #1691
Merged
Conversation
Both released 2026-08-07, and they are coupled: postgraphile@5.1.4 declares grafast ^1.1.2, so neither moves alone. Updated in the ten packages that pin them exactly and in the workspace override, which have to agree — the packages are what downstream consumes (constructive-db resolves this stack from @constructive-io/*), the override is what collapses upstream's wide peer ranges to one copy here. Nothing else in the stack has moved: grafserv, graphile-build, graphile-build-pg, graphile-config, graphile-utils, pg-sql2, pg-introspection, tamedevil, @dataplan/* and @graphile/lru are all already at their latest. graphql stays on 16. Every package in the stack declares graphql ^16.9.0, so 17 is not available to us regardless of what npm calls latest. Verified: grafast and postgraphile resolve to exactly one version each, frozen-lockfile is clean, tsc and pnpm-policy check pass. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V6watrJsLurfsr3uhnqibB
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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.
Last step of the Graphile alignment work. Pairs with constructive-io/constructive-db#2972 — land this one first, since that repo consumes what this one publishes.
What and why
grafastpostgraphileBoth released 2026-08-07, and they are coupled:
postgraphile@5.1.4declaresgrafast: ^1.1.2, so neither moves alone.Updated in the ten packages that pin them exactly and in the workspace override. Both have to agree: the package manifests are what downstream consumes (constructive-db resolves this stack from
@constructive-io/*), while the override is what collapses upstream's wide peer ranges into a single copy here.Nothing else in the stack has moved
grafserv,graphile-build,graphile-build-pg,graphile-config,graphile-utils,pg-sql2,pg-introspection,tamedevil,@dataplan/pg,@dataplan/json,@graphile/lru— all already at their latest published versions.graphql stays on 16
npm calls
graphql@17.0.2latest, but every package in this stack —grafast,postgraphile,graphile-build,@dataplan/pg— declaresgraphql: ^16.9.0, andgraphql-upload@13caps at 16 as well. 17 is not available to us until Graphile ships support. The16.13.0pin is the ecosystem ceiling, not caution.Verification
dist/package.jsoncopies also carry these pins but are gitignored build artifacts, so the diff is the ten source manifests plus the override.🤖 Generated with Claude Code
https://claude.ai/code/session_01V6watrJsLurfsr3uhnqibB