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

Update dependency graphiql to v1 #11

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

Conversation

mend-for-github-com[bot]
Copy link

@mend-for-github-com mend-for-github-com bot commented Jul 9, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
graphiql (source) ^0.14.2 -> ^1.0.0 age adoption passing confidence

By merging this PR, the below vulnerabilities will be automatically resolved:

Severity CVSS Score CVE
High High 7.5 CVE-2020-7760
Medium Medium 6.5 CVE-2022-1365
Medium Medium 6.1 CVE-2022-0235
Medium Medium 5.3 CVE-2020-15168
Medium Medium 5.3 CVE-2022-21670
Medium Medium 4.7 CVE-2021-41248

Release Notes

graphql/graphiql (graphiql)

v1.4.7

Compare Source

Patch Changes

v1.4.6

Compare Source

Patch Changes

v1.4.5

Compare Source

Patch Changes

v1.4.4

Compare Source

Patch Changes

v1.4.3

Compare Source

Patch Changes
  • 6a459f4c #​1968 Thanks @​acao! - Remove optionalDependencies entirely, remove subscriptions-transport-ws which introduces vulnerabilities, upgrade @n1ru4l/push-pull-async-iterable-iterator to 3.0.0, upgrade graphql-ws several minor versions - the [email protected] upgrade will come in a later minor release.
  • eb2d91fa #​1914 Thanks @​harshithpabbati! - fix: history can now be saved even when query history panel is not opened feat: create a new maxHistoryLength prop to allow more than 20 queries in history panel

v1.4.2

Patch Changes

v1.4.1

Patch Changes
  • dd9397e4 #​1819 Thanks @​acao! - GraphiQL.createClient() accepts custom legacyClient, exports typescript types, fixes #​1800.

    createGraphiQLFetcher now only attempts an graphql-ws connection when only subscriptionUrl is provided. In order to use graphql-transport-ws, you'll need to provide the legacyClient option only, and no subscriptionUrl or wsClient option.

v1.4.0

Patch Changes

v1.3.2

Compare Source

Note: Version bump only for package graphiql

v1.3.1

Compare Source

Note: Version bump only for package graphiql

v1.3.0

Compare Source

Features

v1.2.2

Compare Source

Note: Version bump only for package graphiql

v1.2.1

Compare Source

Bug Fixes
  • display schema description if available (050c506)
  • fix linting issue (7117b7c)

v1.2.0

Compare Source

Features

v1.1.0

Compare Source

Bug Fixes
  • improve props in GraphiQL readme (b9b2c8d)
Features
  • graphiql: add prop for adding toolbar content while preserving the default buttons (ea81056)
  • deeper fragment merging (238d0b5)

v1.0.6

Compare Source

Bug Fixes
  • enable variable editor when header editor is not enabled (#​1682) (205fbad)

v1.0.5

Compare Source

Note: Version bump only for package graphiql

v1.0.4

Compare Source

Bug Fixes

v1.0.3

Compare Source

Bug Fixes

v1.0.2

Compare Source

Note: Version bump only for package graphiql

v1.0.1

Compare Source

Bug Fixes

v1.0.0

Compare Source

Bug Fixes

v0.17.5

Compare Source

Note: Version bump only for package graphiql

v0.17.4

Compare Source

Bug Fixes
  • graphiql babel test ignore paths (e1588d9)

v0.17.3

Compare Source

Bug Fixes
  • express-graphql version (e9848b0)
  • test output, webpack resolution, clean build (3b1c2c1)

v0.17.2

Compare Source

Bug Fixes
  • ensure css files move with babel dist (ca95547)
  • remove css from downstream components. soon to be replaced w styled (e765543)

v0.17.1

Compare Source

Bug Fixes

v0.17.0

Compare Source

Bug Fixes
Features
  • graphiql: Prettify also formats query variables (b7d0bfd)

v0.16.0

Compare Source

Bug Fixes
Features
0.15.1 (2019-10-04)
Bug Fixes

v0.15.1


  • If you want to rebase/retry this PR, check this box

@mend-for-github-com mend-for-github-com bot added the security fix Security fix generated by Mend label Jul 9, 2023
@mend-for-github-com
Copy link
Author

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock
No /opt/buildpack/tools/yarn-slim/1.22.19/bin/yarn defined - aborting

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
security fix Security fix generated by Mend
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants