build(deps): bump @graphql-inspector/core from 6.4.1 to 7.0.0

[dependabot]

Bumps @graphql-inspector/core from 6.4.1 to 7.0.0.

Changelog

Sourced from @​graphql-inspector/core's changelog.

7.0.0

Major Changes

• #2893 ef13125 Thanks @​jdolle! - This is a major change to @graphql-inspector/core and introduces a new @graphql-inspector/patch package, which applies changes output from diff on top of a schema -- essentially rebasing these changes onto any schema.

  These changes include:

  • Numerous adjustments to Change types to create more accurate severity levels, such as a boolean indicating if the change applies to a new type or an existing type.
  • Adjustmented the "path" on several change types in order to consistently map to the exact AST node being changed. For example, EnumValueDeprecationReasonAdded's path previously referenced the enumValue (e.g. EnumName.value), not the deprecated directive (e.g. EnumName.value.@deprecated).
  • Added new attributes in order to provide enough context for a new "@​graphql-inspector/patch" function to apply changes accurately.
  • Added support for repeatable directives
  • Includes all nested changes in diff output when a new node is added. This can dramatically increase the number of changes listed which can be noisy, but it makes it possible for "@​graphql-inspector/patch" to apply all changes from a schema. This can be optionally filtered using a newly exported DiffRule.simplifyChanges rule.

  For example, given an existing schema:

  type User {
    id: ID!
    name: String!
  }

  And a diff schema:

  type User {
    id: ID!
    name: String!
    address: Address
  }
  type Address {
  line1: String!
  line2: String!
  }

... (truncated)

Commits

• eae6e1e chore(release): update monorepo packages versions (#2911)
• 2fc8b25 Add Apollo Federation V2 support (#2900)
• ef13125 Add patch package to apply diff changes to schemas; improve accuracy of seve...
• See full diff in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

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.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[dependabot]

Superseded by #8990.