-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
chore(deps): bump the npm_and_yarn group with 4 updates #1649
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
Conversation
Bumps the npm_and_yarn group with 5 updates: | Package | From | To | | --- | --- | --- | | [@sentry/browser](https://github.com/getsentry/sentry-javascript) | `8.33.0` | `8.33.1` | | [cookie](https://github.com/jshttp/cookie) | `0.6.0` | `0.7.1` | | [express](https://github.com/expressjs/express) | `4.21.0` | `4.21.1` | | [secp256k1](https://github.com/cryptocoinjs/secp256k1-node) | `4.0.3` | `5.0.1` | | [secp256k1](https://github.com/cryptocoinjs/secp256k1-node) | `5.0.0` | `5.0.1` | Updates `@sentry/browser` from 8.33.0 to 8.33.1 - [Release notes](https://github.com/getsentry/sentry-javascript/releases) - [Changelog](https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md) - [Commits](getsentry/sentry-javascript@8.33.0...8.33.1) Updates `cookie` from 0.6.0 to 0.7.1 - [Release notes](https://github.com/jshttp/cookie/releases) - [Commits](jshttp/cookie@v0.6.0...v0.7.1) Updates `express` from 4.21.0 to 4.21.1 - [Release notes](https://github.com/expressjs/express/releases) - [Changelog](https://github.com/expressjs/express/blob/4.21.1/History.md) - [Commits](expressjs/express@4.21.0...4.21.1) Updates `secp256k1` from 4.0.3 to 5.0.1 - [Release notes](https://github.com/cryptocoinjs/secp256k1-node/releases) - [Commits](cryptocoinjs/secp256k1-node@v4.0.3...v5.0.1) Updates `secp256k1` from 5.0.0 to 5.0.1 - [Release notes](https://github.com/cryptocoinjs/secp256k1-node/releases) - [Commits](cryptocoinjs/secp256k1-node@v4.0.3...v5.0.1) --- updated-dependencies: - dependency-name: "@sentry/browser" dependency-type: direct:production dependency-group: npm_and_yarn - dependency-name: cookie dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: express dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: secp256k1 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: secp256k1 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@sentry/browser@8.33.0 |
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is network access?This module accesses the network. Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
Superseded by #1662. |
Bumps the npm_and_yarn group with 5 updates:
8.33.0
8.33.1
0.6.0
0.7.1
4.21.0
4.21.1
4.0.3
5.0.1
5.0.0
5.0.1
Updates
@sentry/browser
from 8.33.0 to 8.33.1Release notes
Sourced from
@sentry/browser
's releases.Changelog
Sourced from
@sentry/browser
's changelog.Commits
606cc3a
release: 8.33.19de1a8f
Merge pull request #13861 from getsentry/prepare-release/8.33.12903036
meta(changelog): Update changelog for version 8.33.15c06bd2
fix(core): Update trpc middleware types (#13859)0b739c5
fix(fetch): Fix memory leak when handling endless streaming (#13809)febdfc6
Merge pull request #13853 from getsentry/master4604f3e
Merge branch 'release/8.33.0'237ad53
ci(deps): bump denoland/setup-deno from 1.4.1 to 1.5.1 (#13843)Updates
cookie
from 0.6.0 to 0.7.1Release notes
Sourced from cookie's releases.
Commits
cf4658f
0.7.16a8b8f5
Allow leading dot for domain (#174)58015c0
Remove more code and perf wins (#172)ab057d6
0.7.05f02ca8
Migrate history to GitHub releasesa5d591c
Migrate history to GitHub releases51968f9
Skip isNaN9e7ca51
perf(parse): cache length, return early (#144)d6f39b0
Fix tests for old node6bb701f
Remove failing scorecardMaintainer changes
This version was pushed to npm by blakeembrey, a new releaser for cookie since your current version.
Updates
express
from 4.21.0 to 4.21.1Release notes
Sourced from express's releases.
Changelog
Sourced from express's changelog.
Commits
8e229f9
4.21.1a024c8a
fix(deps): cookie@0.7.1Updates
secp256k1
from 4.0.3 to 5.0.1Release notes
Sourced from secp256k1's releases.
Commits
b3f874f
5.0.19a15fff
elliptic: fix key verification in loadCompressedPublicKeydc37f41
Update elliptic to 6.5.7 (CVE-2024-42461) (#206)6d3474b
5.0.03482be9
Fix segfaults when used with worker_threads (#195)4afabb4
docs: fix example of unrelated public/private pair (#192)Updates
secp256k1
from 5.0.0 to 5.0.1Release notes
Sourced from secp256k1's releases.
Commits
b3f874f
5.0.19a15fff
elliptic: fix key verification in loadCompressedPublicKeydc37f41
Update elliptic to 6.5.7 (CVE-2024-42461) (#206)6d3474b
5.0.03482be9
Fix segfaults when used with worker_threads (#195)4afabb4
docs: fix example of unrelated public/private pair (#192)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major version
will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor version
will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>
will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>
will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>
will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.