You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
getOctokit factory function — Available directly in the script context. Create additional authenticated Octokit clients with different tokens for multi-token workflows, GitHub App tokens, and cross-org access. See Creating additional clients with getOctokit for details and examples.
Orchestration ID in user-agent — The ACTIONS_ORCHESTRATION_ID environment variable is automatically appended to the user-agent string for request tracing.
Breaking changes:
require('@​actions/github') no longer works in scripts. The upgrade to @actions/github v9 (ESM-only) means require('@​actions/github') will fail at runtime. If you previously used patterns like const { getOctokit } = require('@​actions/github') to create secondary clients, use the new injected getOctokit function instead — it's available directly in the script context with no imports needed.
getOctokit is now an injected function parameter. Scripts that declare const getOctokit = ... or let getOctokit = ... will get a SyntaxError because JavaScript does not allow const/let redeclaration of function parameters. Use the injected getOctokit directly, or use var getOctokit = ... if you need to redeclare it.
If your script accesses other @actions/github internals beyond the standard github/octokit client, you may need to update those references for v9 compatibility.
What's Changed
Add ACTIONS_ORCHESTRATION_ID to user-agent string by @Copilot in #695
ci: use deployment: false for integration test environments by @salmanmkc in #712
make octokit instance available as octokit on top of github, to make it easier to seamlessly copy examples from GitHub rest api or octokit documentations by @iamstarkov in #508
Node 20 support is dropped in this release. Node 22 comes with require() support for ESM, which
means it's easier to integrate ES modules into applications. Therefore, it is safe to start using
ESM-only packages.
If you are a user, please upgrade to Node 22. If you are a lib maintainer and see ESM vs CJS
issues when running Jest tests, try using Vitest.
When multiple files match documents pattern, and there are syntax errors in some but not others,
then the operations with errors are not included in the loaded documents list by default
(noSilentErrors: false). This is annoying for users as there is no feedback loop during
development.
noSilentErrors: true is used as the default for Codegen users to make the feedback loop faster.
It can still overriden in Codegen Config if desired.
externalDocuments declares GraphQL documents that will be read but will not have type files
generated for them. These documents are available to plugins for type resolution (e.g. fragment
types), but no output files will be generated based on them. Accepts the same formats as documents.
This config option is useful for monorepos where each project may want to generate types for its
own documents, but some may need to read shared fragments from across projects.
#10618e804925 Thanks @PalmerTurley34! - Honor per-output preset importExtension and emitLegacyCommonJSImports config instead of always using the root config values.
Previously, on partial or full failure, watch mode still write to output. However, since the output'd be an empty array, it will then call removeStaleFiles internally to remove all previously generated files.
This patch puts a temporary fix to avoid writing output on any failure to fix the described behaviour.
This also means the config.allowPartialOutputs does not work in watch mode for now.
#10150e324382 Thanks @ArminWiebigke! - Allow functions to be passed as valid values for UrlSchemaOptions.customFetch. This was already possible, but the type definitions did not reflect that correctly.
#10358157c823 Thanks @eddeee888! - Remove extraneous error stacktrace if fails to load @parcel/watcher
Node 20 support is dropped in this release. Node 22 comes with require() support for ESM, which
means it's easier to integrate ES modules into applications. Therefore, it is safe to start using
ESM-only packages.
If you are a user, please upgrade to Node 22. If you are a lib maintainer and see ESM vs CJS
issues when running Jest tests, try using Vitest.
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code EOVERRIDE
npm error Override for jsdom@29.1.1 conflicts with direct dependency
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-05-25T06_00_44_593Z-debug-0.log
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
This review is AI-generated. Please use common sense when accepting these suggestions, as they may not always be accurate or appropriate for your specific context.
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
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 contains the following updates:
v8.0.0→v9.0.0^5.0.6→^7.0.0^6.0.0→^7.0.0^5.0.0→^6.0.0^6.0.0→^7.0.011.1.4→12.1.011.1.4→12.1.07.3.8→9.2.20.12.0→17.3.020.9.0→25.9.1^22.10.7→^25.0.014.1.24→20.1.10.0.6→1.5.0^8.0.2→^9.0.09.31.0→10.4.03.7.0→4.4.429.7.0→30.4.19.11.0→12.6.015.14.0→17.6.016.0.0→17.0.00.16.1→17.3.026.1.0→29.1.1^5.42.2→^6.0.04.0.13→6.1.25.0.9→6.1.311.1.4→12.1.0^5.2.2→^6.0.05.7.3→6.0.3^5.8.3→^6.0.0^1.0.1→^4.0.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
🔡 If you wish to disable git hash updates, add
":disableDigestUpdates"to the extends array in your config.Release Notes
actions/github-script (@actions/github-script)
v9.0.0Compare Source
New features:
getOctokitfactory function — Available directly in the script context. Create additional authenticated Octokit clients with different tokens for multi-token workflows, GitHub App tokens, and cross-org access. See Creating additional clients withgetOctokitfor details and examples.ACTIONS_ORCHESTRATION_IDenvironment variable is automatically appended to the user-agent string for request tracing.Breaking changes:
require('@​actions/github')no longer works in scripts. The upgrade to@actions/githubv9 (ESM-only) meansrequire('@​actions/github')will fail at runtime. If you previously used patterns likeconst { getOctokit } = require('@​actions/github')to create secondary clients, use the new injectedgetOctokitfunction instead — it's available directly in the script context with no imports needed.getOctokitis now an injected function parameter. Scripts that declareconst getOctokit = ...orlet getOctokit = ...will get aSyntaxErrorbecause JavaScript does not allowconst/letredeclaration of function parameters. Use the injectedgetOctokitdirectly, or usevar getOctokit = ...if you need to redeclare it.@actions/githubinternals beyond the standardgithub/octokitclient, you may need to update those references for v9 compatibility.What's Changed
New Contributors
Full Changelog: actions/github-script@v8.0.0...v9.0.0
v8.0.0Compare Source
v7.1.0Compare Source
What's Changed
actions/upload-artifactby @joshmgross in #512npm audit fixby @joshmgross in #515permissionsin workflows and update actions by @joshmgross in #531octokitREADME updates for v7 by @joshmgross in #557scriptby @joshmgross in #603New Contributors
Full Changelog: actions/github-script@v7...v7.1.0
dotansimha/graphql-code-generator (@graphql-codegen/cli)
v7.0.0Compare Source
Major Changes
#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: Update deps to latest, some
only support ESM
Node 20 support is dropped in this release. Node 22 comes with
require()support for ESM, whichmeans it's easier to integrate ES modules into applications. Therefore, it is safe to start using
ESM-only packages.
If you are a user, please upgrade to Node 22. If you are a lib maintainer and see ESM vs CJS
issues when running Jest tests, try using Vitest.
#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: Drop Node 20 support
#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: Set
noSilentErrors: trueby default
When multiple files match documents pattern, and there are syntax errors in some but not others,
then the operations with errors are not included in the loaded documents list by default
(
noSilentErrors: false). This is annoying for users as there is no feedback loop duringdevelopment.
noSilentErrors: trueis used as the default for Codegen users to make the feedback loop faster.It can still overriden in Codegen Config if desired.
Patch Changes
#10496
afaace6Thanks @eddeee888! - dependencies updates:
@inquirer/prompts@^8.3.2↗︎ (from^7.8.2, independencies)chalk@^5.6.0↗︎ (from^4.1.0, independencies)debounce@^3.0.0↗︎ (from^2.0.0, independencies)detect-indent@^7.0.0↗︎ (from^6.0.0,in
dependencies)listr2@​^10.2.1↗︎ (from^9.0.0, independencies)log-symbols@^7.0.0↗︎(from
^4.0.0, independencies)ts-log@^3.0.0↗︎ (from^2.2.3, independencies)yargs@^18.0.0↗︎ (from^17.0.0, independencies)#10496
afaace6Thanks @eddeee888! - dependencies updates:
chalk@^5.6.0↗︎ (from^4.1.0, independencies)debounce@^3.0.0↗︎ (from^2.0.0, independencies)detect-indent@^7.0.0↗︎ (from^6.0.0,in
dependencies)listr2@​^10.2.1↗︎ (from^9.0.0, independencies)log-symbols@^7.0.0↗︎(from
^4.0.0, independencies)ts-log@^3.0.0↗︎ (from^2.2.3, independencies)yargs@^18.0.0↗︎ (from^17.0.0, independencies)#10496
afaace6Thanks @eddeee888! - dependencies updates:
@inquirer/prompts@^8.3.2↗︎ (from^7.8.2, independencies)#10496
afaace6Thanks @eddeee888! - Use ESM for CLI instead of CJS;
For backwards compatibility;
graphql-codegen-esmis reserved, and alsographql-codegen-cjsisadded for users who want to use CJS.
So the commands are;
graphql-codegen- ESM version, defaultgraphql-codegen-esm- ESM version, same as above, but reserved for backwards compatibilitygraphql-codegen-cjs- CJS version, for users who want to use CJS, but not recommended for newusers. Will be removed in the future.
gql-gen- ESM version, same asgraphql-codegengraphql-code-generator- ESM version, same asgraphql-codegenandgql-genUpdated dependencies
[
afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6,afaace6]:v6.3.1Compare Source
Patch Changes
be85118Thanks @eddeee888! - Fix issue where same SDL in different
documents are ignored when handling documents vs externalDocuments
v6.3.0Compare Source
Minor Changes
#10659
e65d303Thanks @ikusakov2! - Add support for
externalDocumentsexternalDocumentsdeclares GraphQL documents that will be read but will not have type filesgenerated for them. These documents are available to plugins for type resolution (e.g. fragment
types), but no output files will be generated based on them. Accepts the same formats as
documents.This config option is useful for monorepos where each project may want to generate types for its
own documents, but some may need to read shared fragments from across projects.
Patch Changes
[
9a66574,9a66574,9a66574,e65d303]:v6.2.1Compare Source
Patch Changes
e804925Thanks @PalmerTurley34! - Honor per-output presetimportExtensionandemitLegacyCommonJSImportsconfig instead of always using the root config values.v6.2.0Compare Source
Minor Changes
8c4db2aThanks @ikusakov2! - Allow GraphQLSchema to be passed directly to generate({schema: ...}) functionPatch Changes
8c4db2a]:v6.1.3Compare Source
Patch Changes
cdf5dc5Thanks @ardatan! - dependencies updates:@graphql-tools/apollo-engine-loader@^8.0.28↗︎ (from^8.0.0, independencies)@graphql-tools/code-file-loader@^8.1.28↗︎ (from^8.0.0, independencies)@graphql-tools/git-loader@^8.0.32↗︎ (from^8.0.0, independencies)@graphql-tools/github-loader@^9.0.6↗︎ (from^9.0.0, independencies)@graphql-tools/graphql-file-loader@^8.1.11↗︎ (from^8.0.0, independencies)@graphql-tools/json-file-loader@^8.0.26↗︎ (from^8.0.0, independencies)@graphql-tools/load@^8.1.8↗︎ (from^8.1.0, independencies)@graphql-tools/url-loader@^9.0.6↗︎ (from^9.0.0, independencies)@graphql-tools/utils@^11.0.0↗︎ (from^10.0.0, independencies)graphql-config@^5.1.6↗︎ (from^5.1.1, independencies)cdf5dc5,cdf5dc5,cdf5dc5]:v6.1.2Compare Source
Patch Changes
e173e11Thanks @ya2s! - Fix GraphQL Config loading to forward nestedextensions.codegen.configoptionswhen loading schemas/documents, matching
codegen.tsbehavior.v6.1.1Compare Source
Patch Changes
#10569
8cb7d43Thanks @etr2460! - fix(graphql-codegen-cli): Don't hang when 0 CPUs are foundFixes generation when 0 CPUs are returned by os.cpus(), which occurs in sandbox environments.
v6.1.0Compare Source
Minor Changes
9e70bcbThanks @nickmessing! - add importExtension configuration optionPatch Changes
9e70bcb]:v6.0.2Compare Source
Patch Changes
aad7f03Thanks @renovate! - dependencies updates:@graphql-tools/github-loader@^9.0.0↗︎ (from^8.0.0, independencies)@graphql-tools/url-loader@^9.0.0↗︎ (from^8.0.0, independencies)v6.0.1Compare Source
Patch Changes
#10468
cb1b9d9Thanks @eddeee888! - In watch mode, do not write output on failurePreviously, on partial or full failure, watch mode still write to output. However, since the output'd be an empty array, it will then call
removeStaleFilesinternally to remove all previously generated files.This patch puts a temporary fix to avoid writing output on any failure to fix the described behaviour.
This also means the
config.allowPartialOutputsdoes not work in watch mode for now.v6.0.0Compare Source
Major Changes
#10218
140298aThanks @eddeee888! - Drop @graphql-tools/prisma-loader#10218
140298aThanks @eddeee888! - AddallowPartialOutputsflag to partially write successful generation to files#10218
140298aThanks @eddeee888! - Migrate inquirer to @inquirer/prompts#10218
140298aThanks @eddeee888! - Bump dependencies major versions:#10218
140298aThanks @eddeee888! - Bump listr2 to v9#10218
140298aThanks @eddeee888! - Drop Node 18 supportPatch Changes
140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a,140298a]:v5.0.7Compare Source
Patch Changes
#10150
e324382Thanks @ArminWiebigke! - Allow functions to be passed as valid values forUrlSchemaOptions.customFetch. This was already possible, but the type definitions did not reflect that correctly.#10358
157c823Thanks @eddeee888! - Remove extraneous error stacktrace if fails to load@parcel/watcherUpdated dependencies [
e324382,98392fc]:dotansimha/graphql-code-generator (@graphql-codegen/plugin-helpers)
v7.0.1Compare Source
Patch Changes
6ed420aThanks @eddeee888! - Fix FederationTypes not having typesPrefix
and typesSuffix applied
v7.0.0Compare Source
Major Changes
#10496
afaace6Thanks @eddeee888! - BREAKING CHANGE: Update deps to latest, some
only support ESM
Node 20 support is dropped in this release. Node 22 comes with
require()support for ESM, whichmeans it's easier to integrate ES modules into applications. Therefore, it is safe to start using
ESM-only packages.
If you are a user, please upgrade to Node 22. If you are a lib maintainer and see ESM vs CJS
issues when running Jest tests, try using Vitest.
[#10496](https://redirect.github.com/dotansimha/graphql-code-generator/
Configuration
📅 Schedule: (in timezone America/Los_Angeles)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.