Update graphql-tag: 2.10.1 → 2.11.0 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ graphql-tag (2.10.1 → 2.11.0) · Repo · Changelog

Release Notes

2.11.0

• package.json sideEffects changes to clearly identify that graphql-tag doesn't have side effects.
  @hwillson in #313

2.10.4 (from changelog)

• Bump dev/peer deps to accommodate graphql 15.
  @adriencohen in #299

2.10.3

v2.10.3

• Further adjustments to the TS index.d.ts declaration file.
  @Guillaumez in #289

2.10.2

v2.10.2

• Update/fix the existing TS index.d.ts declaration file.
  @hwillson in #285

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 25 commits:

• Merge pull request #313 from apollographql/side-effects
• Clearly identify that `graphql-tag` doesn't have side effects
• Bump js-yaml from 3.10.0 to 3.13.1 (#287)
• Add a package-lock.json file.
• Bump lodash from 4.17.4 to 4.17.19 (#310)
• Version bump, changelog update, prep for publish
• fix(deps): update to graphql@15 (#299)
• Cleaning up the README a bit (#246)
• Version bump, prep for publish
• Fix gql typing (#289)
• Bump version, prep for publish
• Update/fix the existing TS declaration file (#285)
• Remove package lock
• Add package lock
• Merge pull request #286 from apollographql/ci-cleanup
• Just test the main `gql` export
• Minor license tweak
• Stop testing EOL versions of Node
• Stop testing multiple `graphql-js` versions
• Updating out of date urls (#245)
• Updated CRA2 preprocess ability (#233)
• Add CHANGELOG.md credit for @rocwang.
• Update CHANGELOG.md for v2.10.1.
• Add yarn-error.log to .gitignore.
• Update `yarn.lock` with new `integrity` attributes.

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Circle CI, Semaphore and Travis-CI are all excellent options.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #31.