Bumping babel-eslint and pinning graphql-config
#101
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
jnwng
changed the title
graphql-config
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.
I still dont have Renovate set up, so manually bumping a couple of libraries that have been giving us some trouble in Node v4/v5.
Pinning
graphql-configto~1.0.0(no minors) because1.1.0introduces a dependency that doesn't quite work in Node v4/v5. I'm imagining that deprecating support for Node v4 should be a major version bump, otherwise we'll wait until bothgraphql-configandgraphql-importsupport Node v4/v5/v6.TODO:
[ ] Make sure all of the significant new logic is covered by tests[ ] Update CHANGELOG.md with your change[ ] If this was a change that affects the external API, update the README