Version Packages - #3064
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
June 8, 2026 09:18
0888f6a to
abb8391
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
7 times, most recently
from
July 1, 2026 10:09
b02212d to
b6cfa15
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
11 times, most recently
from
July 13, 2026 11:05
429ee5d to
4681377
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
July 13, 2026 13:47
096bb30 to
1bd131a
Compare
Releases: @dataplan/json@1.0.1 @dataplan/pg@1.1.0 @graphile/simplify-inflection@9.0.0 grafast@1.1.0 grafserv@1.0.1 graphile-build-pg@5.1.0 graphile-build@5.1.0 graphile-config@1.1.0 graphile-utils@5.0.2 graphile@5.1.0 pgl@5.0.1 postgraphile@5.1.0 ruru@2.0.1
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 13, 2026 14:16
1bd131a to
42c977c
Compare
benjie
enabled auto-merge
July 13, 2026 14:20
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@graphile/simplify-inflection@9.0.0
Major Changes
#3027
1309c91Thanks @maximsmol! - Fix a bug in singular
relation inflection (in both directions) that would lead to frequent naming
conflicts - the new behavior better reflects that of the PostGraphile V4
simplify plugin.
REMEMBER: once you've chosen an inflection plugin, you should not do any
semver major updates, since those (like this one) may change naming
conventions. Make sure that you export your schema as SDL both before and
after the update, compare, and if they don't match then consider reverting to
the older version of the plugin.
@dataplan/pg@1.1.0
Minor Changes
dd3db66Thanks @benjie! - Add 'oid' as a builtin type.
Patch Changes
#3089
24a9481Thanks @benjie! - Domain codecs can now indicate
if they have a default value.
#3071
3dff681Thanks @benjie! - Previously we used
rootValue()to represent the Query type; but in GraphQL.js rootValue can benull/undefined. Typically you just need a truthy value, so we now use an empty
object.
Updated dependencies
[
9446f64,d5fa38b,56f8add,1a9b835,ccbbd7c,3b56a51,e60e2ed,f0d1f48,8b3904d]:grafast@1.1.0
Minor Changes
e60e2edThanks @benjie! -
coalesceoptimized to providenon-looping execute for small numbers of steps, and now returns
constant(null)when called with 0 steps.Patch Changes
#3065
9446f64Thanks @benjie! -
fieldArgsare now created inthe root plan and applied in the layer plan of the target step; this fixes an
issue where fieldArgs could not be applied to step with side effects.
#3061
56f8addThanks @benjie! - Exposes rootValueStep on
OperationPlan and removes some transient values from being stored. Adds new
global
variableValues()step retriever, useful for helping produceGraphQLResolveInfo and similar.
#3070
1a9b835Thanks @benjie! - Stop using deprecated
GraphQLError signature
#3103
ccbbd7cThanks @benjie! - Throw better errors when a step
class calls
this.addDependency(...)but doesn't actually pass a step todepend on. (Previously: "cannot access property
layerPlanof undefined" orsimilar errors were thrown.)
#3072
3b56a51Thanks @benjie! - Grafast no longer coerces
rootValueto a mutable object, increasing compatibility with legacyresolvers.
#3069
f0d1f48Thanks @benjie! - Remove vestigial
insideGraphQLcode.#3062
8b3904dThanks @benjie! - Internals: clear
__TrackedValueStep initialValue on finalize.
Updated dependencies
[
350dd8d,5f95b1c]:graphile-build@5.1.0
Minor Changes
c21f24cThanks @benjie! -
makeSchemanow awaits thewriting of the SDL if enabled by
exportSchemaSDLPathPatch Changes
#3092
79b234eThanks @benjie! - getTypeByName is now allowed to
be called during construction of a scalar.
#3071
3dff681Thanks @benjie! - Previously we used
rootValue()to represent the Query type; but in GraphQL.js rootValue can benull/undefined. Typically you just need a truthy value, so we now use an empty
object.
Updated dependencies
[
350dd8d,5f95b1c]:graphile-build-pg@5.1.0
Minor Changes
#3084
dd3db66Thanks @benjie! - Add 'oid' as a builtin type.
#3098
75444acThanks @benjie! - Fix: index behaviors plugin
updated so that only attributes (columns) on tables, materialized views and
foreign tables are scanned for indexes; all other types (including composite
types, views, ...) are given the benefit of the doubt.
This might result in more fields showing up in your schema.
Patch Changes
#3065
9446f64Thanks @benjie! -
fieldArgsare now created inthe root plan and applied in the layer plan of the target step; this fixes an
issue where fieldArgs could not be applied to step with side effects.
#3088
d3d4376Thanks @benjie! - Add
pgResource.extensions.isView,.isMaterializedView,.isForeignTablesoplugins can determine which resources came from views/materialized
views/foreign tables.
#3086
65527f8Thanks @benjie! - Add
build.dataplanJsonproperty - a copy of
@dataplan/json#3099
4b5b673Thanks @benjie! - PostGraphile will only throw an
error when it fails to read enum table values from a table in a published
schema (one in the
schemaslist in your pgServices); enum tables in otherschemas will result in a warning instead (since during the gather phase we
don't know whether or not they will be needed come schema build time).
#3089
24a9481Thanks @benjie! - Domain codecs can now indicate
if they have a default value.
#3063
d3156dfThanks @benjie! - Improve scopes around
PgMutationCreatePlugin
Updated dependencies
[
350dd8d,5f95b1c]:postgraphile@5.1.0
Minor Changes
#3084
dd3db66Thanks @benjie! - Add 'oid' as a builtin type.
#3098
75444acThanks @benjie! - Fix: index behaviors plugin
updated so that only attributes (columns) on tables, materialized views and
foreign tables are scanned for indexes; all other types (including composite
types, views, ...) are given the benefit of the doubt.
This might result in more fields showing up in your schema.
#3081
557791fThanks @benjie! - V4 preset now supports
@omitsmart tags with spaces between values (e.g.
@omit create, update, deleterather than
@omit create,update,delete)#3097
b28eb75Thanks @benjie! - V4 preset now also grants
+filterProcbehavior when@filterableis present. Fixes compatibility withpostgraphile-plugin-connection-filter.#3090
35d8b3eThanks @benjie! - Bugfix: the V4 preset now
correctly ignores
@omit selectlike V4 would. Previously, the V4 presetwould silently turn
@omit selectinto-select, which differs to V4'shandling of this. (Note:
@omit readis probably what you're looking for,@omit selectis silently ignored.)#3060
c21f24cThanks @benjie! -
makeSchemanow awaits thewriting of the SDL if enabled by
exportSchemaSDLPathPatch Changes
#3065
9446f64Thanks @benjie! -
fieldArgsare now created inthe root plan and applied in the layer plan of the target step; this fixes an
issue where fieldArgs could not be applied to step with side effects.
#3088
d3d4376Thanks @benjie! - Add
pgResource.extensions.isView,.isMaterializedView,.isForeignTablesoplugins can determine which resources came from views/materialized
views/foreign tables.
#3099
4b5b673Thanks @benjie! - PostGraphile will only throw an
error when it fails to read enum table values from a table in a published
schema (one in the
schemaslist in your pgServices); enum tables in otherschemas will result in a warning instead (since during the gather phase we
don't know whether or not they will be needed come schema build time).
#3089
24a9481Thanks @benjie! - Domain codecs can now indicate
if they have a default value.
#3071
3dff681Thanks @benjie! - Previously we used
rootValue()to represent the Query type; but in GraphQL.js rootValue can benull/undefined. Typically you just need a truthy value, so we now use an empty
object.
#3077
5f95b1cThanks @benjie! - CLIs will now correctly
auto-import
graphile.config.mtsfiles (previouslygraphile.config.tsfilesworked, but
graphile.config.mtsfiles would be ignored). With all majorversions of Node.js now having native support for type stripping and
require(esm), we recommend moving your configuration files to TypeScript
(using ESM and erasable syntax only).
#3078
00bb2baThanks @evolkmann! - Export types related to
the
pgSmartTags/etc utils (PgSmartTagRule,PgSmartTagTags,PgSmartTagFilterFunction,JSONPgSmartTags, etc.).#3083
3cbbd88Thanks @benjie! - Add safer assumptions to
@omitbehavior fallbackUpdated dependencies
[
9446f64,dd3db66,d3d4376,d5fa38b,56f8add,1a9b835,ccbbd7c,65527f8,3b56a51,e60e2ed,79b234e,f0d1f48,4b5b673,75444ac,24a9481,3dff681,350dd8d,8b3904d,d3156df,5f95b1c,00bb2ba,c21f24c]:graphile@5.1.0
Minor Changes
e91e92cThanks @benjie! - Fixes formatting of multi-line
types in options output
Patch Changes
#3075
e1a6f37Thanks @benjie! - Don't throw error for
graphile --helpwhen certain libraries are not installed.#3080
350dd8dThanks @benjie! -
GraphileConfig.Preset::pluginsis now marked readonly - we do not require amutable array.
#3077
5f95b1cThanks @benjie! - CLIs will now correctly
auto-import
graphile.config.mtsfiles (previouslygraphile.config.tsfilesworked, but
graphile.config.mtsfiles would be ignored). With all majorversions of Node.js now having native support for type stripping and
require(esm), we recommend moving your configuration files to TypeScript
(using ESM and erasable syntax only).
Updated dependencies
[
350dd8d,5f95b1c]:graphile-config@1.1.0
Minor Changes
5f95b1cThanks @benjie! - CLIs will now correctly
auto-import
graphile.config.mtsfiles (previouslygraphile.config.tsfilesworked, but
graphile.config.mtsfiles would be ignored). With all majorversions of Node.js now having native support for type stripping and
require(esm), we recommend moving your configuration files to TypeScript
(using ESM and erasable syntax only).
Patch Changes
350dd8dThanks @benjie! -
GraphileConfig.Preset::pluginsis now marked readonly - we do not require amutable array.
@dataplan/json@1.0.1
Patch Changes
d5fa38bThanks @benjie! - Add
versionto exportsgrafserv@1.0.1
Patch Changes
#3070
1a9b835Thanks @benjie! - Stop using deprecated
GraphQLError signature
Updated dependencies
[
350dd8d,5f95b1c]:ruru@2.0.1
Patch Changes
5f95b1cThanks @benjie! - CLIs will now correctly
auto-import
graphile.config.mtsfiles (previouslygraphile.config.tsfilesworked, but
graphile.config.mtsfiles would be ignored). With all majorversions of Node.js now having native support for type stripping and
require(esm), we recommend moving your configuration files to TypeScript
(using ESM and erasable syntax only).
[
350dd8d,5f95b1c]:graphile-utils@5.0.2
Patch Changes
00bb2baThanks @evolkmann! - Export types related to
the
pgSmartTags/etc utils (PgSmartTagRule,PgSmartTagTags,PgSmartTagFilterFunction,JSONPgSmartTags, etc.).pgl@5.0.1
Patch Changes
5f95b1cThanks @benjie! - CLIs will now correctly
auto-import
graphile.config.mtsfiles (previouslygraphile.config.tsfilesworked, but
graphile.config.mtsfiles would be ignored). With all majorversions of Node.js now having native support for type stripping and
require(esm), we recommend moving your configuration files to TypeScript
(using ESM and erasable syntax only).
[
9446f64,dd3db66,d3d4376,d5fa38b,56f8add,1a9b835,ccbbd7c,65527f8,3b56a51,e60e2ed,79b234e,f0d1f48,4b5b673,75444ac,24a9481,557791f,b28eb75,3dff681,350dd8d,8b3904d,d3156df,35d8b3e,5f95b1c,00bb2ba,c21f24c,3cbbd88]: