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: Bump up nextjs 14.2.15 #10850

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

Conversation

memoyil
Copy link
Collaborator

@memoyil memoyil commented Oct 21, 2024


PR-Codex overview

This PR focuses on updating the versions of various dependencies, particularly next, to 14.2.15, across multiple configuration files and ensuring consistency in the versioning of related packages.

Detailed summary

  • Updated next from 14.2.14 to 14.2.15 in pnpm-workspace.yaml and pnpm-lock.yaml.
  • Adjusted versions of related packages (@vanilla-extract/next-plugin, next-auth, next-seo, next-themes, etc.) to reflect the change to next@14.2.15.
  • Ensured consistency in versioning across various configurations and lock files.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Copy link

changeset-bot bot commented Oct 21, 2024

⚠️ No Changeset found

Latest commit: a792f56

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Oct 21, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
aptos-web ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 21, 2024 10:46am
blog ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 21, 2024 10:46am
bridge ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 21, 2024 10:46am
games ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 21, 2024 10:46am
gamification ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 21, 2024 10:46am
uikit ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 21, 2024 10:46am
web ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 21, 2024 10:46am

Copy link

Report is too large to display inline.
View full report↗︎

Next steps

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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/which@2.0.2
  • @SocketSecurity ignore npm/ci-info@3.9.0
  • @SocketSecurity ignore npm/argparse@2.0.1
  • @SocketSecurity ignore npm/rimraf@3.0.2
  • @SocketSecurity ignore npm/mkdirp@1.0.4
  • @SocketSecurity ignore npm/yargs-parser@18.1.3
  • @SocketSecurity ignore npm/glob@7.2.3
  • @SocketSecurity ignore npm/source-map-support@0.5.21
  • @SocketSecurity ignore npm/chalk@2.4.2
  • @SocketSecurity ignore npm/mkdirp@0.5.6
  • @SocketSecurity ignore npm/supports-color@5.5.0
  • @SocketSecurity ignore npm/which@1.3.1
  • @SocketSecurity ignore npm/fs.realpath@1.0.0
  • @SocketSecurity ignore npm/inflight@1.0.6
  • @SocketSecurity ignore npm/resolve-from@4.0.0
  • @SocketSecurity ignore npm/external-editor@3.1.0
  • @SocketSecurity ignore npm/chardet@0.7.0
  • @SocketSecurity ignore npm/tmp@0.0.33
  • @SocketSecurity ignore npm/graceful-fs@4.2.11
  • @SocketSecurity ignore npm/locate-path@5.0.0
  • @SocketSecurity ignore npm/path-exists@4.0.0
  • @SocketSecurity ignore npm/cross-spawn@7.0.3
  • @SocketSecurity ignore npm/npm-run-path@4.0.1
  • @SocketSecurity ignore npm/isexe@2.0.0
  • @SocketSecurity ignore npm/pump@3.0.0
  • @SocketSecurity ignore npm/argparse@1.0.10
  • @SocketSecurity ignore npm/readable-stream@3.6.2
  • @SocketSecurity ignore npm/read-pkg@5.2.0
  • @SocketSecurity ignore npm/tunnel-agent@0.6.0
  • @SocketSecurity ignore npm/got@11.8.6
  • @SocketSecurity ignore npm/tar-stream@2.2.0
  • @SocketSecurity ignore npm/readable-stream@2.3.8
  • @SocketSecurity ignore npm/fs-constants@1.0.0
  • @SocketSecurity ignore npm/yauzl@2.10.0
  • @SocketSecurity ignore npm/jsonfile@6.1.0
  • @SocketSecurity ignore npm/path-type@4.0.0
  • @SocketSecurity ignore npm/rc@1.2.8
  • @SocketSecurity ignore npm/yargs-parser@21.1.1
  • @SocketSecurity ignore npm/glob@8.1.0
  • @SocketSecurity ignore npm/bindings@1.5.0
  • @SocketSecurity ignore npm/chownr@2.0.0
  • @SocketSecurity ignore npm/fs-minipass@2.1.0
  • @SocketSecurity ignore npm/chownr@1.1.4
  • @SocketSecurity ignore npm/create-require@1.1.1
  • @SocketSecurity ignore npm/v8-compile-cache-lib@3.0.1
  • @SocketSecurity ignore npm/fd-slicer@1.1.0
  • @SocketSecurity ignore npm/commander@10.0.1
  • @SocketSecurity ignore npm/commander@9.5.0
  • @SocketSecurity ignore npm/ansi-colors@4.1.3
  • @SocketSecurity ignore npm/colorette@1.4.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant