Upcoming Release Changes #396
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
force-pushed
the
changeset-release/master
branch
6 times, most recently
from
f6c6ce1
to
cc8e738
Compare
github-actions
bot
force-pushed
the
changeset-release/master
branch
5 times, most recently
from
75a08d9
to
633f78b
Compare
github-actions
bot
force-pushed
the
changeset-release/master
branch
6 times, most recently
from
def02ae
to
5936f64
Compare
github-actions
bot
force-pushed
the
changeset-release/master
branch
13 times, most recently
from
c6aa035
to
c0394d8
Compare
github-actions
bot
force-pushed
the
changeset-release/master
branch
3 times, most recently
from
63af040
to
f58554c
Compare
github-actions
bot
force-pushed
the
changeset-release/master
branch
from
f58554c
to
7951788
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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 master, this PR will be updated.
Releases
@graphql-eslint/eslint-plugin@1.0.0
Major Changes
14211d6: feat: remove
prettierrule, add related docsBREAKING CHANGE: Remove
prettierRuleSince prettier itself support now linting GraphQL code and syntax, we removed the need for this rule from this package.
For more information, see:
61251e7: BREAKING CHANGE: Remove deprecated rule
validate-against-schema.If you are using
validate-against-schema, please remove it and specify the exact rules that you need.61251e7: Bump dependencies and update minimum Node version to
v12Minor Changes
Patch Changes
9a40163: Fix issues with
avoid-operation-name-prefixand error with caseSensitive1257d51: fix: original file should not be considered as file block
Related Getting ESLint errors about missing files #88
ESLint supports
textdirectly, no need to use the hacky way. See https://github.com/eslint/eslint/blob/master/lib/linter/linter.js#L1298Related
eslint-plugin-prettier's issue hae been fixed at feat: support processor virtual filename prettier/eslint-plugin-prettier#4016d4a356: Fix loadSiblings file location
388a0bf: Support OperationDefinition in naming-convention rule
5ff184b: Fix issues with
lone-schema-definitionrule7a04e1e: Added support for direcrives in
no-unreachable-typesruleef8d776: Fix errors always thrown with unique-type-names rule