chore(deps): upgrade mercurius gateway to v2.1.0 #3093
+27
−147
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Mercurius Gateway has some new options available and those are not reflected by @nestjs/mercurius because of the current version.
Issue Number: N/A
What is the new behavior?
There is no new behavior from @nestjs/mercurius side. You can find Mercurius Gateway changes here
Does this PR introduce a breaking change?
According to the changelogs there are no breaking changes
Other information
eslint-plugin-prettier
to latest v4 because it is not compatible with the current Prettier version (v2.8.8) and it's breaking ESLint. Seems like it was upgraded here by the robot. We have to either upgrade Prettier to v3 or keepeslint-plugin-prettier
v4.Please, let me know if you want me to upgrade Prettier to v3 instead which likely will introduce changes in the format of the files.
NOTE: The build is failing because the
yarn.lock
file was modified due to the upgrades and the CI is running install with--frozen-lockfile