Skip to content

fix(deps): update dependency graphql to v17 - #11902

Open
renovate[bot] wants to merge 6 commits into
mainfrom
renovate/graphql-17.x
Open

fix(deps): update dependency graphql to v17#11902
renovate[bot] wants to merge 6 commits into
mainfrom
renovate/graphql-17.x

Conversation

@renovate

@renovate renovate Bot commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
graphql 16.14.117.0.1 age confidence

Release Notes

graphql/graphql-js (graphql)

v17.0.1

Compare Source

v17.0.1 (2026-06-16)
Bug Fix 🐞
  • #​4824 fix(diagnostics): emit asyncStart after promise settlement to match native tracePromise (@​logaretm)
Internal 🏠
2 PRs were merged
Committers: 2

v17.0.0

Compare Source

v17.0.0 (2026-06-15)
New Feature 🚀
Bug Fix 🐞
Docs 📝
11 PRs were merged
Polish 💅
2 PRs were merged
Internal 🏠
6 PRs were merged
Committers: 3

v16.14.2

Compare Source

v16.14.2 (2026-06-09)

Docs 📝
7 PRs were merged
Polish 💅
Committers: 2

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "every weekday after 2:00 am before 6:00 am,every weekend"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/graphql-17.x branch from 992a561 to c0a9a34 Compare June 19, 2026 22:56
@Betree

Betree commented Jun 22, 2026

Copy link
Copy Markdown
Member

@cursor complete this update

@cursor

cursor Bot commented Jun 22, 2026

Copy link
Copy Markdown

Completed the GraphQL v17 upgrade on renovate/graphql-17.x. Here’s what was fixed:

Changes

  1. Schema validation (Host.location) — GraphQL v17 enforces that if an interface field isn’t deprecated, implementation fields can’t be either. Removed location from the Host fields that were getting a deprecation reason, since Account.location is not deprecated. Updated schemaV2.graphql accordingly.

  2. Input field defaults — GraphQL v17 requires the new GraphQLDefaultInput shape. Updated timezone defaults in:

    • EventCreateInput.ts
    • AccountUpdateInput.js

    From default: 'UTC'default: { value: 'UTC' }

  3. Dependency deduplication — Added an npm override for graphql@17.0.1 so @escape.tech/graphql-armor no longer bundles graphql v16, which was causing ValidationRule type mismatches with Apollo Server in routes.ts.

Verification

  • npm run type:check passes
  • Changes committed and pushed to renovate/graphql-17.x (commit 45e9f670c)

CI should now pass the typescript and lint checks that were failing. The test / test-graphql jobs may still need a database environment to run fully.

Open in Web Open in Cursor 

GraphQL v17 enforces that interface fields cannot be non-deprecated when
implementation fields are deprecated. Remove location from Host fields
that receive a deprecation reason since Account.location is not deprecated.

Update input field defaults to use the new GraphQLDefaultInput shape
({ value: ... }) required by graphql v17.

Add an npm override to dedupe nested graphql@16 packages from
@escape.tech/graphql-armor, fixing ValidationRule type mismatches with
Apollo Server.
@renovate

renovate Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

GraphQL v17 requires interface fields to be deprecated when implementation
fields are. Add deprecation reasons to tiers, stats, and plan on the
CollectiveInterface type to match CollectiveFields.
GraphQL v17 reports missing required variables as invalid values rather
than using the previous "was not provided" message format.
GraphQL v17 uses "has invalid value" instead of "got invalid value" when
reporting variable coercion failures.
GraphQL v17 requires argument defaults to use the default: { value }
shape for VariablesInAllowedPositionRule to recognize them. This fixes
E2E failures where nullable $limit/$offset variables were rejected
against Int! collection arguments (e.g. DashboardVendors query).
@Betree

Betree commented Jun 23, 2026

Copy link
Copy Markdown
Member

Matching frontend PR: opencollective/opencollective-frontend#12271

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants