Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency graphql-sse to v2.5.2 #580

Merged
merged 1 commit into from
Dec 21, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 20, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
graphql-sse 2.5.1 -> 2.5.2 age adoption passing confidence

Release Notes

enisdenjo/graphql-sse (graphql-sse)

v2.5.2

Compare Source

Bug Fixes
  • remove package.json workspaces entry in release (c6dc093)

Configuration

πŸ“… Schedule: Branch creation - "after 8pm every weekday,before 7pm on Sunday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

β™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

πŸ”• Ignore: Close this PR and you won't be reminded about this update again.


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

This PR has been generated by Mend Renovate. View repository job log here.

Copy link

sonarcloud bot commented Dec 20, 2023

Quality Gate Passed Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@renovate renovate bot merged commit a3e028c into main Dec 21, 2023
5 checks passed
@renovate renovate bot deleted the renovate/graphql-sse-2.x-lockfile branch December 21, 2023 00:07
@timonmasberg
Copy link
Member

πŸŽ‰ This PR is included in version 1.0.0 πŸŽ‰

The release is available on GitHub release

Your semantic-release bot πŸ“¦πŸš€

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

1 participant