deps(example): Bump the dependencies group in /examples/nextjs-14-clerk-shield with 5 updates #581
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps the dependencies group in /examples/nextjs-14-clerk-shield with 5 updates: | Package | From | To | | --- | --- | --- | | [@clerk/nextjs](https://github.com/clerk/javascript/tree/HEAD/packages/nextjs) | `4.29.11` | `4.29.12` | | [next](https://github.com/vercel/next.js) | `14.1.4` | `14.2.1` | | [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react) | `18.2.74` | `18.2.78` | | [@types/react-dom](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react-dom) | `18.2.24` | `18.2.25` | | [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next) | `14.1.4` | `14.2.1` | Updates `@clerk/nextjs` from 4.29.11 to 4.29.12 - [Release notes](https://github.com/clerk/javascript/releases) - [Changelog](https://github.com/clerk/javascript/blob/@clerk/nextjs@4.29.12/packages/nextjs/CHANGELOG.md) - [Commits](https://github.com/clerk/javascript/commits/@clerk/nextjs@4.29.12/packages/nextjs) Updates `next` from 14.1.4 to 14.2.1 - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v14.1.4...v14.2.1) Updates `@types/react` from 18.2.74 to 18.2.78 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react) Updates `@types/react-dom` from 18.2.24 to 18.2.25 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react-dom) Updates `eslint-config-next` from 14.1.4 to 14.2.1 - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](https://github.com/vercel/next.js/commits/v14.2.1/packages/eslint-config-next) --- updated-dependencies: - dependency-name: "@clerk/nextjs" dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dependencies - dependency-name: next dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dependencies - dependency-name: "@types/react" dependency-type: direct:development update-type: version-update:semver-patch dependency-group: dependencies - dependency-name: "@types/react-dom" dependency-type: direct:development update-type: version-update:semver-patch dependency-group: dependencies - dependency-name: eslint-config-next dependency-type: direct:development update-type: version-update:semver-minor dependency-group: dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
the
dependencies
|
Merging to
|
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@types/node@20.11.25, npm/express@4.19.2, npm/nextjs-14-pages-wrap@0.1.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. What is new author?A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package. Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. What are floating dependencies?Package has a dependency with a floating version range. This can cause issues if the dependency publishes a new major version. Packages should specify properly semver ranges to avoid version conflicts. What are trivial packages?Packages less than 10 lines of code are easily copied into your own project and may not warrant the additional supply chain risk of an external dependency. Removing this package as a dependency and implementing its logic will reduce supply chain risk. 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 #599. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/examples/nextjs-14-clerk-shield/dependencies-179e9a9ab9
branch
Bumps the dependencies group in /examples/nextjs-14-clerk-shield with 5 updates:
4.29.114.29.1214.1.414.2.118.2.7418.2.7818.2.2418.2.2514.1.414.2.1Updates
@clerk/nextjsfrom 4.29.11 to 4.29.12Release notes
Sourced from
@clerk/nextjs's releases.Changelog
Sourced from
@clerk/nextjs's changelog.Commits
31d893cchore(repo): Version packages (#3138)Updates
nextfrom 14.1.4 to 14.2.1Release notes
Sourced from next's releases.
... (truncated)
Commits
c0ae6f6v14.2.19d7ce74modify scripts597aa44update publish configs14987d9use pathToFileUrl to make esm import()s work with absolute windows paths (#64...774563fv14.2.0ab26234Add documentation for --experimental-debug-memory-usage (#64322)d94466cDocs: Add recommendations for CSS import order (#64321)7aabb1dv14.2.0-canary.67cbee709update turbopack (#64347)83675ceEnsure build-native is in needs properly (#64357)Updates
@types/reactfrom 18.2.74 to 18.2.78Commits
Updates
@types/react-domfrom 18.2.24 to 18.2.25Commits
Updates
eslint-config-nextfrom 14.1.4 to 14.2.1Release notes
Sourced from eslint-config-next's releases.
... (truncated)
Commits
c0ae6f6v14.2.1774563fv14.2.07aabb1dv14.2.0-canary.67265d7b9v14.2.0-canary.6622754fav14.2.0-canary.65167ea33v14.2.0-canary.64c289063v14.2.0-canary.63e46d088v14.2.0-canary.6242f8ac1v14.2.0-canary.61acaf642v14.2.0-canary.60Dependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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