This repository has been archived by the owner on Oct 11, 2022. It is now read-only.
Update graphql-tag: 2.10.1 → 2.12.4 (minor) #31
Closed
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.
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.12.4) · Repo · Changelog
Release Notes
2.12.4
2.11.0
2.10.4 (from changelog)
2.10.3
2.10.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 65 commits:
Version bump; prep for publish
Allow fragments to be imported by name when using the webpack loader (#257)
Bump rollup from 2.41.5 to 2.42.2 (#384)
Bump @types/mocha from 8.2.1 to 8.2.2 (#383)
Bump npm version to 2.12.3.
Bump rollup from 2.41.4 to 2.41.5 (#382)
Update tslib to version 2.1.0. (#381)
Bump npm version to 2.12.2.
Mention PR #380 in CHANGELOG.md.
Avoid using Object.assign to attach extra properties to gql. (#380)
Bump @types/node from 14.14.28 to 14.14.35 (#378)
Bump chai from 4.3.0 to 4.3.4 (#377)
Bump typescript from 4.1.5 to 4.2.3 (#367)
Bump mocha from 8.3.0 to 8.3.2 (#375)
Bump rollup from 2.39.0 to 2.41.4 (#379)
Bump @types/mocha from 8.2.0 to 8.2.1 (#355)
Bump @types/node from 14.14.27 to 14.14.28 (#353)
Bump npm version to 2.12.1.
Avoid TypeScript `import type ...` syntax for now. (#352)
Add "engines": { "node": ">=10" } to package.json (#309)
Bump @types/node from 14.14.22 to 14.14.27 (#351)
Bump rollup from 2.38.5 to 2.39.0 (#349)
Bump mocha from 8.2.1 to 8.3.0 (#350)
Fix the npm pack (#338)
Bump @types/node from 14.14.22 to 14.14.26 (#348)
Bump @types/chai from 4.2.14 to 4.2.15 (#347)
Bump chai from 4.2.0 to 4.3.0 (#341)
Bump typescript from 4.1.3 to 4.1.5 (#346)
Bump rollup from 2.38.1 to 2.38.5 (#343)
Update LICENSE year and company name.
Bump npm version to 2.12.0.
Set up dependabot to keep dependencies up-to-date.
Merge pull request #325 from PowerKiKi/master
Mention PR #325 in CHANGELOG.md.
Avoid using direct eval in tests.
Convert repo to TypeScript.
Implement ES6 export file
Remove no-longer-used .travis.yml configuration file.
Set up GitHub Actions.
Rename graphql-js to graphql (#318)
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:
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