deps(example): Bump the dependencies group across 1 directory with 4 updates #1929
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
dependencies
|
Merging to
|
|
New dependencies detected. Learn more about Socket for GitHub ↗︎
|
|
🚨 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 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 is unstable ownership?A new collaborator has begun publishing package versions. Package stability and security risk may be elevated. Try to reduce the amount of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm. What is an install script?Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. 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
|
…updates Bumps the dependencies group with 4 updates in the /examples/nextjs-14-clerk-rl directory: [@clerk/nextjs](https://github.com/clerk/javascript/tree/HEAD/packages/nextjs), [next](https://github.com/vercel/next.js), [@types/react-dom](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react-dom) and [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next). Updates `@clerk/nextjs` from 5.7.1 to 5.7.3 - [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 `next` from 14.2.14 to 14.2.15 - [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.2.14...v14.2.15) Updates `@types/react-dom` from 18.3.0 to 18.3.1 - [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.2.14 to 14.2.15 - [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.15/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-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-patch dependency-group: dependencies ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/examples/nextjs-14-clerk-rl/dependencies-ae54775139
branch
from
d931258 to
1b08712
Compare
|
Looks like these dependencies are updatable in another way, so this is no longer needed. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/examples/nextjs-14-clerk-rl/dependencies-ae54775139
branch
Bumps the dependencies group with 4 updates in the /examples/nextjs-14-clerk-rl directory: @clerk/nextjs, next, @types/react-dom and eslint-config-next.
Updates
@clerk/nextjsfrom 5.7.1 to 5.7.3Release notes
Sourced from
@clerk/nextjs's releases.Changelog
Sourced from
@clerk/nextjs's changelog.Commits
0d923c1ci(repo): Version packages (#4323)d724a36ci(repo): Version packages (#4307)0d56455fix(nextjs): do not build test file declarations (#4286)3b6d510chore(repo): Node 20 / attw change (#4283)Updates
nextfrom 14.2.14 to 14.2.15Release notes
Sourced from next's releases.
Commits
737c29ev14.2.151c8234ebackport: [i18n] Routing fix #70761 (#70976)bb3f580fix: Do not omit alt on getImgProps return type, ImgProps (#70818)cb8113bfix(next/image): handle undefinedimages.localPatternsconfig in `images-ma...9c1191afix missing helpers innext-test-utils.ts0de4183fix linte03c4fffeat(next/image): addimages.localPatternsconfig (#70802)540ea2dbackport: support breadcrumb style catch-all parallel routes (#65063) (#70794)0d0448bFix client reference access causing metadata missing (#70732) (#70788)381d1f9feat(next/image): add support fordecodingprop (#70678)Updates
@types/react-domfrom 18.3.0 to 18.3.1Commits
Updates
eslint-config-nextfrom 14.2.14 to 14.2.15Release notes
Sourced from eslint-config-next's releases.
Commits
737c29ev14.2.15Dependabot 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