The Vue core team has tagged v3.6.0-rc.10, the tenth release candidate in the run-up to the stable 3.6.0 release. This build lands on the minor branch's pre-release track, meaning it is intended for early adopters and library authors testing compatibility rather than for production deployments.
As with prior release candidates, the release notes direct readers to the changelogs rather than enumerating individual commits in the release body:
- For stable releases, refer to
CHANGELOG.mdin the repository for full details. - For pre-releases, refer to the
CHANGELOG.mdof the minor branch, which tracks the3.6line specifically. - The tag is published under the
vuejs/corerepository, consistent with previous3.6.0-rc.*iterations.
Because the body defers to the changelog, developers wanting the exact list of fixes, refactors, and internal adjustments should open the linked changelog files directly instead of relying on the tag page. The rc suffix signals that the API surface is expected to be feature-complete, so remaining changes are typically bug fixes, regressions from earlier candidates, and polish rather than new capabilities.
Why this matters: release candidates are the point where framework-level changes are cheapest to catch. If you maintain a Vue-based library, a design system, or a large application on the 3.5.x line, pinning a test environment to 3.6.0-rc.10 lets you surface breaking edge cases before stable ships. Tooling authors — Vite plugins, SSR frameworks such as Nuxt, and type-level packages — should verify that their peer dependency ranges and generated types still align with the candidate. Waiting until stable reduces your window to report issues upstream, so early validation on this RC is the practical path to a smooth upgrade.
Source: https://github.com/vuejs/core/releases/tag/v3.6.0-rc.10