Skip to content

Conversation

@greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

graphql-tag just published its new version 1.0.0.

State Update 🚀
Dependency graphql-tag
New version 1.0.0
Type devDependency

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of graphql-tag.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴


The new version differs by 8 commits .

  • 3507847 Releasing as 1.0.0
  • e879f82 Merge pull request #20 from wmertens/patch-1
  • 2029294 gql: minor zipping flow improvement
  • 7a68d78 Version 0.1.17 release
  • c5c45c9 Merge pull request #17 from apollostack/fragment-support
  • 3e109a6 Fixes a new test
  • 420d199 Ensure fragment use doesn't include an unnecessary print
  • 6aa3fbf Support including fragment documents inside gql

See the full diff.


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade

@kamilkisiela kamilkisiela merged commit fe8470b into master Nov 24, 2016
@kamilkisiela kamilkisiela deleted the greenkeeper-graphql-tag-1.0.0 branch November 24, 2016 10:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants