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

chore(deps): Bump the npm_and_yarn group across 1 directory with 3 updates #532

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

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 9, 2025

Bumps the npm_and_yarn group with 2 updates in the /app directory: @clerk/clerk-sdk-node and @clerk/nextjs.

Updates @clerk/clerk-sdk-node from 4.13.22 to 5.1.6

Release notes

Sourced from @​clerk/clerk-sdk-node's releases.

@​clerk/clerk-sdk-node@​5.1.6

Patch Changes

@​clerk/clerk-sdk-node@​5.1.5

Patch Changes

@​clerk/clerk-sdk-node@​5.1.4

Patch Changes

@​clerk/clerk-sdk-node@​5.1.3

Patch Changes

Changelog

Sourced from @​clerk/clerk-sdk-node's changelog.

5.1.6

Patch Changes

5.1.5

Patch Changes

5.1.4

Patch Changes

5.1.3

Patch Changes

5.1.2

Patch Changes

5.1.1

Patch Changes

... (truncated)

Commits

Updates @clerk/nextjs from 4.31.6 to 6.9.8

Release notes

Sourced from @​clerk/nextjs's releases.

@​clerk/nextjs@​6.9.8

Patch Changes

@​clerk/nextjs@​6.9.7

Patch Changes

@​clerk/nextjs@​6.9.6

Patch Changes

@​clerk/nextjs@​6.9.5

Patch Changes

@​clerk/nextjs@​6.9.4

Patch Changes

Changelog

Sourced from @​clerk/nextjs's changelog.

6.9.8

Patch Changes

6.9.7

Patch Changes

6.9.6

Patch Changes

6.9.5

Patch Changes

6.9.4

Patch Changes

... (truncated)

Commits

Updates cookie from 0.5.0 to 0.7.0

Release notes

Sourced from cookie's releases.

0.7.0

jshttp/cookie@v0.6.0...v0.7.0

0.6.0

  • Add partitioned option
Commits
Maintainer changes

This version was pushed to npm by blakeembrey, a new releaser for cookie since your current version.


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 conditions
    You can disable automated security fix PRs for this repo from the Security Alerts page.

…dates

Bumps the npm_and_yarn group with 2 updates in the /app directory: [@clerk/clerk-sdk-node](https://github.com/clerk/javascript/tree/HEAD/packages/sdk-node) and [@clerk/nextjs](https://github.com/clerk/javascript/tree/HEAD/packages/nextjs).


Updates `@clerk/clerk-sdk-node` from 4.13.22 to 5.1.6
- [Release notes](https://github.com/clerk/javascript/releases)
- [Changelog](https://github.com/clerk/javascript/blob/main/packages/sdk-node/CHANGELOG.md)
- [Commits](https://github.com/clerk/javascript/commits/@clerk/[email protected]/packages/sdk-node)

Updates `@clerk/nextjs` from 4.31.6 to 6.9.8
- [Release notes](https://github.com/clerk/javascript/releases)
- [Changelog](https://github.com/clerk/javascript/blob/main/packages/nextjs/CHANGELOG.md)
- [Commits](https://github.com/clerk/javascript/commits/@clerk/[email protected]/packages/nextjs)

Updates `cookie` from 0.5.0 to 0.7.0
- [Release notes](https://github.com/jshttp/cookie/releases)
- [Commits](jshttp/cookie@v0.5.0...v0.7.0)

---
updated-dependencies:
- dependency-name: "@clerk/clerk-sdk-node"
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: "@clerk/nextjs"
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: cookie
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jan 9, 2025
Copy link

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteCI
License Policy Violation npm/@codesandbox/[email protected]
  • License: Elastic-2.0 - Not allowed by license policy (package/LICENSE)
⚠︎

View full report↗︎

Next steps

What is a license policy violation?

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Take a deeper look at the dependency

Take 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 package

If 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 risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants