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

[Snyk] Upgrade cloudevents from 6.0.3 to 6.0.4 #191

Merged
merged 1 commit into from
Mar 17, 2023

Conversation

lholmquist
Copy link
Member

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade cloudevents from 6.0.3 to 6.0.4.

ℹ️ 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 2023-02-16.
Release notes
Package name: cloudevents from cloudevents GitHub release notes
Commit messages
Package name: cloudevents
  • 870d211 6.0.4
  • 78b8e0a chore: release 6.0.3 (#524)
  • 953bc2a chore: Typos
  • bc3aaca chore: added the engines property to the package.json
  • e5ee836 fix: This fixes bug #525 where the browser version was breaking becuase of process not being found. (#526)
  • b374d9a chore(examples): add mqtt example (#523)
  • 64e527c build(deps): bump cookiejar from 2.1.3 to 2.1.4 (#521)
  • 1b449c4 build(deps): bump http-cache-semantics from 4.1.0 to 4.1.1 (#522)
  • eccc00e build(deps): bump json5 from 2.2.0 to 2.2.3 (#520)
  • 94f1a3d build(deps): bump qs and formidable (#518)

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

@lance lance merged commit d5f96da into main Mar 17, 2023
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.

None yet

3 participants