chore(deps): bump next-intl from 4.13.2 to 4.13.4 - #435
Merged
Conversation
Bumps [next-intl](https://github.com/amannn/next-intl) from 4.13.2 to 4.13.4. - [Release notes](https://github.com/amannn/next-intl/releases) - [Changelog](https://github.com/amannn/next-intl/blob/main/CHANGELOG.md) - [Commits](amannn/next-intl@v4.13.2...v4.13.4) --- updated-dependencies: - dependency-name: next-intl dependency-version: 4.13.4 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
CI installs with Node 20 (npm 10), which keeps next-intl's nested optional-peer @swc/helpers entry; Dependabot generates the lockfile with npm 11, which drops it, so `npm ci` fails as out-of-sync before any of lint/typecheck/test/build runs. Regenerated with npm 10 — the only diff is re-adding that nested entry. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
`main` moved next 16.2.6 → 16.2.12 (#441) and applied transitive audit fixes (#442) since this branch was cut, so both manifests conflicted. Resolved by keeping main's `next` and this branch's `next-intl`, then regenerating package-lock.json from the merged package.json with npm 10 — the version CI's Node 20 ships, so the nested optional-peer @swc/helpers entry `npm ci` needs is preserved. Verified next 16.2.12, next-intl 4.13.4, and every audit-fixed transitive version from #442 survive, and `npm ci` succeeds. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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-intl from 4.13.2 to 4.13.4.
Release notes
Sourced from next-intl's releases.
Changelog
Sourced from next-intl's changelog.
Commits
7fa175dv4.13.482de47ffix: AvoidusePathname()reads for non-locale-switching links, avoiding unn...89ae783v4.13.30555acefix: Next.js 16.3 compatibility preparation (only update locale cookie for do...89c72b1docs: Add AI agents page, integrate eloqnt studio, and update nav (#2357)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)