Skip to content
This repository has been archived by the owner on Jun 15, 2023. It is now read-only.

[Snyk] Upgrade graphql-tag from 2.12.4 to 2.12.5 #189

Open
wants to merge 1 commit into
base: v5
Choose a base branch
from

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade graphql-tag from 2.12.4 to 2.12.5.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 21 days ago, on 2021-06-25.
Release notes
Package name: graphql-tag
  • 2.12.5 - 2021-06-25
  • 2.12.4 - 2021-04-29
    • Allow fragments to be imported by name when using the webpack loader.
      @ dobesv in #257
from graphql-tag GitHub release notes
Commit messages
Package name: graphql-tag
  • cd2f4d0 Bump npm version to 2.12.5.
  • fda09fc Fix typescript version in package.json.
  • bb7a28b Bump mocha from 8.3.2 to 9.0.1 (#444)
  • 186fa90 Bump graphql from 15.5.0 to 15.5.1 (#443)
  • 55930f3 Mention PR #381 in CHANGELOG.md (#386)
  • a8cd984 Bump @ types/chai from 4.2.15 to 4.2.19 (#441)
  • 95fd781 Bump glob-parent from 5.1.1 to 5.1.2 (#432)
  • 1c4b7d1 Bump hosted-git-info from 2.8.8 to 2.8.9 (#411)
  • 3d4a273 Bump typescript from 4.2.3 to 4.3.4 (#438)
  • dda3817 Bump rollup from 2.42.2 to 2.52.3 (#442)
  • fd3f0eb Bump lodash from 4.17.20 to 4.17.21 (#410)
  • f102010 Also publish src/ directory to npm, for source maps (#403)

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant