Repository navigation
chore(deps): update vue-i18n to 12.0.0-alpha.6 and Vue to 3.6.0-rc.12 - #656
Merged
Merged
Conversation
Move the lockfile from vue-i18n and the @intlify packages 12.0.0-alpha.3 to the current `next`, 12.0.0-alpha.6. The catalog and the dependencies still ask for `next`. With alpha.3 in the lockfile, CI tested an older vue-i18n than the one users install, and any lockfile update, such as the Renovate PRs, failed the tests. - vue-i18n 12.0.0-alpha.6 requires Vue 3.6, so the `vue` catalog moves from ~3.5.34 to ~3.6.0-rc.12. - `overrides` set the @intlify packages, vue-i18n and petite-vue-i18n to `next`, as v11 does with its ranges. Without them, the vue-i18n and petite-vue-i18n installed for the peers of unplugin-vue-i18n stay on alpha.3. - `minimumReleaseAgeExclude` lists the alpha.6 packages: pnpm 11 rejects a lockfile entry for a day after it is published, also on a frozen install. The entries can go after 2026-10-18 15:31 UTC. - Update the test expectations. Since 12.0.0-alpha.4, escapeHtml also escapes `&`, `/` and `=`, and the message compiler reads `\\` as one backslash, as v11 does.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
| Check name | Status | Explanation |
|---|---|---|
| Description Check |  |
Check skipped - CodeRabbit’s high-level summary is enabled. |
| Title check | |
The title clearly and concisely identifies the main changes: updating vue-i18n to 12.0.0-alpha.6 and Vue to 3.6.0-rc.12. |
| Docstring Coverage | |
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1… |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches
-
📝 Generate docstrings
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
commit: |
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.
Summary
Move the lockfile from vue-i18n and the
@intlifypackages 12.0.0-alpha.3 to 12.0.0-alpha.6, the currentnext, and Vue from 3.5.34 to 3.6.0-rc.12. The catalog and the dependencies still ask fornext. With alpha.3 in the lockfile, CI tested an older vue-i18n than the one users install, and any lockfile update (the Renovate PRs, for example) failed the tests.Behavior changes
@intlify/unplugin-vue-i18nnow depends onvue~3.6.0-rc.12instead of~3.5.34(itsvuedependency comes from thevuecatalog). vue-i18n 12.0.0-alpha.6 requires Vue 3.6 (fix!: require Vue 3.6 or later vue-i18n#2691).nextspecifiers of the published packages do not change.Notes
pnpm-workspace.yaml:vuecatalog:~3.5.34→~3.6.0-rc.12.overridesset@intlify/shared,@intlify/message-compiler,@intlify/core-base,@intlify/vue-i18n-core,vue-i18nandpetite-vue-i18ntonext, as v11 does with its~11.4.xranges. Without them, thevue-i18nandpetite-vue-i18nthat pnpm installs for the peers of@intlify/unplugin-vue-i18nstay on alpha.3, which is in their^12.0.0-alpha.2range.minimumReleaseAgeExcludelists the seven alpha.6 packages. pnpm 11 rejects a lockfile entry until a day after it is published (ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION), also onpnpm install --frozen-lockfile, so CI and the release workflow would fail until then. The entries name these versions only, and can be removed after 2026-10-18 15:31 UTC.escape messagein unplugin-vue-i18n. Both changes come from 12.0.0-alpha.4:escapeHtmlof@intlify/sharedalso escapes&,/and=(</p>→</p>).\\as one backslash, as v11 does. Thebackslash-backslashsnapshots now match the ones on v11.Test plan
pnpm install --frozen-lockfilewith the default pnpm 11 settingspnpm build,pnpm test:typecheckpnpm lint(0 errors, 124 warnings, the same as before)pnpm test:unit:utils(147 passed, 3 skipped)pnpm test:unit:unplugin:vite:vite8(83 passed, 3 skipped),vite6(82 passed, 4 skipped),webpackandrspack(57 passed, 29 skipped each), also withCI=truepnpm test:e2e:unplugin(6 passed),pnpm test:e2e(3 passed)pnpm build:example:vite,pnpm build:example:webpack,pnpm build:example:rspackSummary by CodeRabbit