Upcoming Release Changes

[github-actions]

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

@graphql-hive/[email protected]

Minor Changes

• #6637
  5130fc1
  Thanks @n1ru4l! - Add error logging for invalid combinations of the
  target and token configuration.

  • Please make sure to provide the target option for usage reporting when using a token that
    starts with hvo1/.
  • Please make sure to not provide a target option for usage reporting when a token does
    not start with hvo1/

Patch Changes

• Updated dependencies
  [5130fc1]:
  • @graphql-hive/[email protected]

@graphql-hive/[email protected]

Minor Changes

• #6658
  e6a970f
  Thanks @n1ru4l! - Internal adjustments for using non-deprecated API
  fields.

• #6626
  2056307
  Thanks @jdolle! - Show dangerous changes as a separate list in
  schema:check

• #6662
  2b220a5
  Thanks @n1ru4l! - Support federation composition validation for
  IMPLEMENTED_BY_INACCESSIBLE.

• #6675
  ed66171
  Thanks @kamilkisiela! - Updates the
  @theguild/federation-composition to v0.18.1 that includes the following changes:

  • Support progressive overrides (@override(label: "<value>"))
  • Allow to use @composeDirective on a built-in scalar (like @oneOf)
  • Performance improvements (lazy compute of errors), especially noticeable in large schemas (2s ->
    600ms)
  • Ensure nested key fields are marked as @shareable
  • Stop collecting paths when a leaf field was reached (performance improvement)
  • Avoid infinite loop when entity field returns itself

Patch Changes

• Updated dependencies
  [5130fc1]:
  • @graphql-hive/[email protected]

@graphql-hive/[email protected]

Minor Changes

• #6637
  5130fc1
  Thanks @n1ru4l! - Add error logging for invalid combinations of the
  target and token configuration.

  • Please make sure to provide the target option for usage reporting when using a token that
    starts with hvo1/.
  • Please make sure to not provide a target option for usage reporting when a token does
    not start with hvo1/

@graphql-hive/[email protected]

Minor Changes

• #6637
  5130fc1
  Thanks @n1ru4l! - Add error logging for invalid combinations of the
  target and token configuration.

  • Please make sure to provide the target option for usage reporting when using a token that
    starts with hvo1/.
  • Please make sure to not provide a target option for usage reporting when a token does
    not start with hvo1/

Patch Changes

• Updated dependencies
  [5130fc1]:
  • @graphql-hive/[email protected]

@graphql-hive/[email protected]

Minor Changes

• #6637
  5130fc1
  Thanks @n1ru4l! - Add error logging for invalid combinations of the
  target and token configuration.

  • Please make sure to provide the target option for usage reporting when using a token that
    starts with hvo1/.
  • Please make sure to not provide a target option for usage reporting when a token does
    not start with hvo1/

Patch Changes

• Updated dependencies
  [5130fc1]:
  • @graphql-hive/[email protected]

[email protected]

Minor Changes

• #6626
  2056307
  Thanks @jdolle! - Add target breaking change setting to turn
  dangerous changes into breaking changes

• #6658
  e6a970f
  Thanks @n1ru4l! - Adjust GraphQL schema according to schema design
  policies.

• #6701
  f2fe6c8
  Thanks @n1ru4l! - Print dangerous schema changes as own section in
  github changes.

• #6662
  2b220a5
  Thanks @n1ru4l! - Support federation composition validation for
  IMPLEMENTED_BY_INACCESSIBLE.

• #6678
  8fd9ad0
  Thanks @n1ru4l! - Deprecate CriticalityLevel scalar and fields
  referencing it in favor of the SeverityLevelType scalar. Expose SchemaChange.severityLevel and
  SchemaChange.severityReason via the public API endpoint.

• #6614
  c1d9c05
  Thanks @n1ru4l! - Add new route /graphql-public to the server
  service which contains the public GraphQL API (fields and types will follow).

• #6675
  ed66171
  Thanks @kamilkisiela! - Updates the
  @theguild/federation-composition to v0.18.1 that includes the following changes:

  • Support progressive overrides (@override(label: "<value>"))
  • Allow to use @composeDirective on a built-in scalar (like @oneOf)
  • Performance improvements (lazy compute of errors), especially noticeable in large schemas (2s ->
    600ms)
  • Ensure nested key fields are marked as @shareable
  • Stop collecting paths when a leaf field was reached (performance improvement)
  • Avoid infinite loop when entity field returns itself

• #6665
  cb41478
  Thanks @kamilkisiela! - Update
  @theguild/federation-composition to v0.16.0.

  • Support Apollo Federation v2.7, but without the progressive @override.
  • Support Apollo Federation v2.8, but without the @context and @fromContext directives.
  • Support Apollo Federation v2.9, including @cost and @listSize directives.

• #6683
  ab774b7
  Thanks @jdolle! - Make url optional for subsequent federated schema
  publishes

Patch Changes

• #6716
  1767037
  Thanks @jdolle! - Improve slack alert error logs

• #6687
  349b78f
  Thanks @jdolle! - Improve resource ID tooltip behavior

• #6685
  a107ad3
  Thanks @n1ru4l! - Fix failing schema contract composition.

• #6602
  df3e5a2
  Thanks @jdolle! - Added directions for publishing on no schema
  component

• #6713
  4f9aeae
  Thanks @jdolle! - Do not store empty metadata in db

• #6660
  5ff2aaa
  Thanks @jdolle! - fix schedule a meeting link

• #6718
  fd9b160
  Thanks @jdolle! - upgrade 'got' package to fix TimeoutError case

• #6632
  9b2bec6
  Thanks @jdolle! - Capture Stripe.js load error to avoid raising an
  unhandled error

• #6706
  4435820
  Thanks @n1ru4l! - Improve contract schema building for subgraphs
  using the extend keyword.

[email protected]

Patch Changes

• #6714
  3f823c9
  Thanks @github-actions! - Updated internal Apollo crates
  to get downstream fix for advisories. See
  https://github.com/apollographql/router/releases/tag/v2.1.1

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.