Repository navigation
Version Packages - #631
Merged
Merged
Version Packages#631
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 8, 2026 14:43
ed07825 to
722f6af
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 8, 2026 16:01
722f6af to
59b82c4
Compare
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-worker@0.18.0
Minor Changes
#628
bc98aafThanks @benjie! - Now published as pure ESM, but
worry not as unflagged require(ESM) is now enabled by default in
Node 20.19.0+,
Node 22.12.0+ and Node 24+ so
everything should continue to work as before.
#628
bc98aafThanks @benjie! - For consistency,
cosmiconfigis no longer supported for configuration; use
graphile.config.tsinstead.(This release will throw errors if you're using cosmisconfig, in later
releases cosmiconfigs will not be detected.)
#628
bc98aafThanks @benjie! - TypeScript task files with
.tsand.mtsextensions are now recognized by default and loaded throughNode's native type stripping if possible. Only erasable, verbatim TypeScript
syntax is supported without a custom loader or precompilation.
.js,.cjsand
.mjsfiles are prioritised ahead of.tsand.mtsfiles.#628
bc98aafThanks @benjie! - We now use the
exportsoption, meaning sub-path imports (
require("graphile-worker/...")) are nolonger supported. If you need something not exported by default, raise an
issue.
#628
bc98aafThanks @benjie! - Since Node 20 is EOL, Node 22
is now the minimum supported version, per our
requirements documentation.
#628
bc98aafThanks @benjie! -
LogLevelexport is now typeonly - a string union rather than a TypeScript const enum.
#628
bc98aafThanks @benjie! -
Runnergains[Symbol.asyncDispose]()method, so you canawait using runner = await run(...)and the worker will be released when youreach the end of the scope. (Primarily useful for tests.)
Patch Changes
#628
bc98aafThanks @benjie! - Fix issue where enabling
localQueuecould cause jobs from the same named queue to run concurrently(violating the serial execution guarantee for named queues): a single batch
fetch could lock multiple jobs belonging to one named queue. Batch fetches now
return at most one job per named queue
(#621).
#628
bc98aafThanks @benjie! - Maintenance work: upgrade to
latest TypeScript, Jest, eliminate ts-node, fix yargs, use erasable syntax
only for type-stripping support.