chore(deps): bump next from 15.5.14 to 15.5.18 in /web#918
Merged
Conversation
Bumps [next](https://github.com/vercel/next.js) from 15.5.14 to 15.5.18. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v15.5.14...v15.5.18) --- updated-dependencies: - dependency-name: next dependency-version: 15.5.18 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
the
dependencies
dependabot
Bot
added
dependencies
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| "gray-matter": "^4.0.3", | ||
| "lucide-react": "^1.0.1", | ||
| "next": "15.5.14", | ||
| "next": "15.5.18", |
Contributor
There was a problem hiding this comment.
🔴 package-lock.json not updated after bumping next version
The web directory is a workspace defined in the root package.json:30-33, so the root package-lock.json is the lockfile governing its dependencies. The PR bumps next from 15.5.14 to 15.5.18 in web/package.json but does not update package-lock.json, which still contains 30 references to 15.5.14 and zero references to 15.5.18. This means npm ci (used in CI/CD) will fail because the lockfile is out of sync with the declared dependency, or npm install will resolve to a different version than intended.
Prompt for agents
The root package-lock.json needs to be regenerated to reflect the next version bump from 15.5.14 to 15.5.18. Since web/ is a workspace in the root package.json (see workspaces field at root package.json:30-33), the root lockfile governs all workspace dependencies. Run `npm install` from the repository root to update package-lock.json, then include the updated lockfile in this PR. Without this, `npm ci` in CI will fail due to the lockfile being out of sync with web/package.json.
Was this helpful? React with 👍 or 👎 to provide feedback.
Dependabot updated web/package.json to next@15.5.18 but did not regenerate the root package-lock.json, causing npm ci to fail with "Missing: postcss@8.4.31 from lock file" across License Compliance, NPM Audit, and Deploy Preview jobs. Regenerate the lockfile so npm ci can install next@15.5.18 and its transitive deps cleanly.
…w2SnF # Conflicts: # package-lock.json
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps next from 15.5.14 to 15.5.18.
Release notes
Sourced from next's releases.
Commits
9ff92cev15.5.1800ebe23[backport] Disable build caches for production/staging/force-preview deploys ...62c97abv15.5.17423623aTurbopack: Match proxy matchers with webpack implementation (#93594)fa78739Turbopack: Fix middleware matcher suffix (#93590)36e62c6[backport] Turbopack: more strict vergen setup (#93588)36589b5[backport][test] Pin package manager to patch versions (#93596)ad6fd4ev15.5.1679d7dffIgnore malformed CSP nonce headers (#103)c4f6908router-server: guard upgrade proxy against absolute-url SSRF (#77) (#102)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for next 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.