Repository navigation
chore(deps-dev): bump @graphql-codegen/core from 6.2.2 to 7.0.0 - #964
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@graphql-codegen/core](https://github.com/dotansimha/graphql-code-generator/tree/HEAD/packages/graphql-codegen-core) from 6.2.2 to 7.0.0. - [Release notes](https://github.com/dotansimha/graphql-code-generator/releases) - [Changelog](https://github.com/dotansimha/graphql-code-generator/blob/master/packages/graphql-codegen-core/CHANGELOG.md) - [Commits](https://github.com/dotansimha/graphql-code-generator/commits/@graphql-codegen/core@7.0.0/packages/graphql-codegen-core) --- updated-dependencies: - dependency-name: "@graphql-codegen/core" dependency-version: 7.0.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Collaborator
Medformatik
added a commit
that referenced
this pull request
Nov 15, 2026
…raphQL Code Generator 8 (#968) ## What changed and why This PR applies all eight Dependabot PRs from today's run (#960–#967) in one branch, so CI runs once. Four of them were red: the lockfile-only and minor bumps failed the release-information gate and the stale SDK check, and the four GraphQL Code Generator majors broke code generation because each moved only one package. **Minor and patch updates (#960, #961, #962, #963).** These cover the 13-package minor-and-patch group, Biome 2.6.6, TanStack Query 5.107.1 and MapLibre GL 6.17.0, all at the versions Dependabot proposed. Two follow-ups were needed: - orval 8.47.0 now types a request body whose schema has no properties as `{ [key: string]: never }` instead of `{ [key: string]: unknown }`. The 13 affected admin SDK files are regenerated with `pnpm sdk:generate`. No code outside the generated SDK uses these types, and the core and web typechecks pass. - The extension CLI bundles parse5 through core, and parse5 moves to 8.1.1. I compared the built bundle with main's: parse5 is the only change, so this PR adds a patch Changeset for `@openmapx/extension-cli`. commander 15.1.0 stays an external runtime dependency. - `biome.json` now points at the 2.6.6 schema. **GraphQL Code Generator 8 (#964, #965, #966, #967, major).** I checked the [CLI 8.0.0](https://github.com/dotansimha/graphql-code-generator/blob/master/packages/graphql-codegen-cli/CHANGELOG.md), core 7.0.0, typed-document-node 8.0.0 and typescript-operations 7.0.0 changelogs against both generators: - The breaking change that matters is that a plugin's `validate` now receives `outputFile` inside an info object, not as the fourth argument. Each Dependabot PR moved only one package, so the CLI and the plugins disagreed, and `typed-document-node` failed with "The `path` argument must be of type string". All four packages now move together. - The OTP generator also uses the community `@graphql-codegen/typescript-generic-sdk` plugin, whose 5.x `validate` reads the old argument. It moves to 6.0.1, whose [changelog](https://github.com/dotansimha/graphql-code-generator-community/blob/main/packages/plugins/typescript/generic-sdk/CHANGELOG.md) names the v8 migration as its only breaking change. The 6.0.1 `documentMode: 'string'` remap does not apply, because the generator uses `documentNode`. 6.0.1 was published two days ago, inside the repository's 7-day cooldown. `graphql-codegen-typescript-validation-schema` exports no `validate`, so it is unaffected. - The other breaking changes do not apply. Both generators already run on graphql 16 or 17 and Node 24. Neither uses `emitLegacyCommonJSImports` or an array value in `generates`, and neither loads documents from code files, so the new `#graphql` template extraction has nothing to find. `generate()` now returns `FileOutput[] | void`, which the plain-JavaScript Entur script already handles. - Regenerating with the new stack leaves every committed Entur and OTP file unchanged. ## Related work Supersedes #960, #961, #962, #963, #964, #965, #966 and #967. ## Verification - `pnpm install --frozen-lockfile` passes. The lockfile was rebuilt from main's, so only the proposed packages and the codegen majors' new transitive dependencies change, such as graphql-tools 9 and the Babel 8 parser it brings. No existing package was re-resolved. - `node scripts/entur/codegen.mjs --check` passes, and `pnpm otp:generate` produces no diff. - `scripts/otp/codegen.test.ts` passes (16/16). It failed for all five OTP profiles before `typescript-generic-sdk` moved to 6. - `pnpm sdk:generate` reports the API SDK families as current after regeneration. - The packages/core and apps/web typechecks pass, apart from apps/web's generated licences JSON, which needs a build. - `biome ci .` passes on Biome 2.6.6. - The extension CLI bundle was compared with main's: only the bundled parse5 differs. - Left to CI: the full node, web and mobile test projects, the database suites and the image builds. ## Release and upgrade impact Product impact: ordinary Dependency updates only. The extension CLI's patch release carries the bundled parse5 8.1.1.
Collaborator
|
Superseded by #968, which is merged. |
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/graphql-codegen/core-7.0.0
branch
November 15, 2026 23:22
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Bumps @graphql-codegen/core from 6.2.2 to 7.0.0.
Changelog
Sourced from @graphql-codegen/core's changelog.
... (truncated)
Commits
e5a5669chore(release): update monorepo packages versions (#11085)fa49a37Next major feature branch (#11075)cbefcf3Revert "chore: update@graphql-toolsto latest majors and drop Node below 22....1161d66chore: update@graphql-toolsto latest majors and drop Node below 22.18 and g...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)