-
Notifications
You must be signed in to change notification settings - Fork 43
Bump next from 14.2.25 to 14.2.32 #1078
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
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 0eccd54:
|
moeodeh3
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not related to your pr but a lot of missing ^ for some reason in some examples - more of a note so feel free to ignore
| "esm": "^3.2.25", | ||
| "install": "^0.13.0", | ||
| "next": "14.2.25", | ||
| "next": "14.2.32", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: not your doing but why no ^ here?
| "clsx": "^2.1.0", | ||
| "lucide-react": "^0.426.0", | ||
| "next": "14.2.25", | ||
| "next": "14.2.32", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same goes for here
| "dotenv": "^16.0.3", | ||
| "lucide-react": "^0.542.0", | ||
| "next": "14.2.25", | ||
| "next": "14.2.32", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and here
| "esm": "^3.2.25", | ||
| "install": "^0.13.0", | ||
| "next": "14.2.25", | ||
| "next": "14.2.32", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
woah there are a lot of these
Bumps [next](https://github.com/vercel/next.js) from 14.2.25 to 14.2.32. - [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.25...v14.2.32) --- updated-dependencies: - dependency-name: next dependency-version: 14.2.32 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
dada6f7 to
0eccd54
Compare
Bumps next from 14.2.25 to 14.2.32.
updated-dependencies:
Summary & Motivation
per #1076
How I Tested These Changes
Did you add a changeset?
If updating one of our packages, you'll likely need to add a changeset to your PR. To do so, run
pnpm changeset.pnpm changesetwill generate a file where you should write a human friendly message about the changes. Note how this (example) includes the package name (should be auto added by the command) along with the type of semver change (major.minor.patch) (which you should set).These changes will be used at release time to determine what packages to publish and how to bump their version. For more context see this comment.