build(deps-dev): bump @graphql-inspector/core from 3.1.2 to 4.0.0

[dependabot]

Bumps @graphql-inspector/core from 3.1.2 to 4.0.0.

Release notes

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

v3.4.0

• cli: New audit command #2164

v3.3.0

• docker: Publish images to the registry
• core: Fix Cannot convert object to primitive value error for defaultValue in ChangeType.InputFieldDefaultValueChanged
• action: Fix ignored approve-label for push events #2133
• core: Addition of non-nullable argument with a default is now dangerous (previously breaking) #2137

v3.2.0

• action: Use GitHub REST API to retrieve the full blob content if schema is truncated #2131
• action: Diffing a graphql endpoint with a local .json schema file results in an error, fixed in #2090
• core: Fix comparison of non-nullable fields #2122
• core: Fix removal of a deprecated input field #2122

v3.1.4

• core: Fix regression #2128 introduced in #2100

v3.1.3

• core: Fix missing export of safeUnreachable rule #2063
• core: Fix equality for objects #2100

Changelog

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

4.0.0

Major Changes

• #2341 b17ee0a3 Thanks @​velias! - fix: core bump to patch coverage

3.5.1

Patch Changes

• #2302 dd840130 Thanks @​renovate! - dependencies updates:
  • Updated dependency object-inspect@1.12.3 ↗︎ (from 1.10.3, in dependencies)

3.5.0

Minor Changes

• #2240 ca29cdd1 Thanks @​Tohaker! - suppressRemovalOfDeprecatedField rule will now mark removed types as dangerous

Commits

• c92ed4c chore(release): update monorepo packages versions (#2342)
• 1118f36 coverage: provide overall statistics about coverage (#2184)
• db38f97 chore(release): update monorepo packages versions (#2284)
• dd84013 fix(deps): update dependency object-inspect to v1.12.3 (#2302)
• bd0cb29 chore(deps): update dependency @​theguild/eslint-config to v0.8.0 (#2244)
• a803c30 chore(deps): update dependency @​theguild/prettier-config to v1.1.1 (#2255)
• d893a71 ESlint rules fixes (#2229)
• fb71261 chore(release): update monorepo packages versions (#2248)
• ca29cdd Marking breaking types as dangerous with the deprecated fields rule (#2240)
• 93087f6 Refactor release flow and use changeset to manage versioning (#2231)
• Additional commits viewable 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 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)

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.