chore: upgrade PostGraphile/Graphile ecosystem from RC to stable releases#921
Merged
pyramation merged 1 commit intomainfrom Mar 27, 2026
Merged
Conversation
…ases - postgraphile: 5.0.0-rc.10 → 5.0.0 - grafast: 1.0.0-rc.9 → 1.0.0 - grafserv: 1.0.0-rc.7 → 1.0.0 - graphile-build: 5.0.0-rc.6 → 5.0.0 - graphile-build-pg: 5.0.0-rc.8 → 5.0.0 - graphile-config: 1.0.0-rc.6 → 1.0.0 - graphile-utils: 5.0.0-rc.8 → 5.0.0 - @dataplan/json: 1.0.0-rc.6 → 1.0.0 - @dataplan/pg: 1.0.0-rc.8 → 1.0.0 - pg-sql2: 5.0.0-rc.5 → 5.0.0 - tamedevil: 0.1.0-rc.6 → 0.1.0 - @graphile/simplify-inflection: 8.0.0-rc.5 → 8.0.0 Also removes unused postgraphile-plugin-connection-filter dependency from graphql/server (the codebase uses the local graphile-connection-filter workspace package instead). Note: @graphile-contrib/pg-many-to-many remains at 2.0.0-rc.2 as no stable release is available yet.
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
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.
Summary
Upgrades 12 PostGraphile/Graphile ecosystem packages from release candidate versions to their official stable releases across 15 workspace packages:
postgraphile5.0.0-rc.105.0.0grafast1.0.0-rc.91.0.0grafserv1.0.0-rc.71.0.0graphile-build5.0.0-rc.65.0.0graphile-build-pg5.0.0-rc.85.0.0graphile-config1.0.0-rc.61.0.0graphile-utils5.0.0-rc.85.0.0@dataplan/json1.0.0-rc.61.0.0@dataplan/pg1.0.0-rc.81.0.0pg-sql25.0.0-rc.55.0.0tamedevil0.1.0-rc.60.1.0@graphile/simplify-inflection8.0.0-rc.58.0.0Also removes
postgraphile-plugin-connection-filterfromgraphql/server— it had zero imports in the codebase; the localgraphile-connection-filterworkspace package is used instead.Still on RC (no stable available):
@graphile-contrib/pg-many-to-many(2.0.0-rc.2)Review & Testing Checklist for Human
postgraphile-plugin-connection-filterremoval is safe: Confirm it isn't loaded indirectly via PostGraphile presets/config (grep showed zero imports, but plugins can be auto-discovered). Check thatgraphile-connection-filter(workspace) fully replaces it.@graphile-contrib/pg-many-to-many@2.0.0-rc.2compatibility: This package remains on RC while its Graphile peer deps moved to stable — verify it resolves correctly and doesn't cause runtime issues.pnpm buildpasses, but the GraphQL server, codegen pipeline, and query execution should be smoke-tested end-to-end to catch any behavioral differences between the last RC and stable.Notes
ruru,ruru-types, and@graphile/lrualso moved from RC to stable in the lockfile automatically.package.jsonversion bumps + lockfile update.Link to Devin session: https://app.devin.ai/sessions/f3d1694a9af54fdea06c9914634460eb
Requested by: @pyramation