The Vue core team has published v3.6.0-rc.9, the ninth release candidate in the 3.6.0 pre-release line. The tag is available on the vuejs/core GitHub repository and is intended for early testing rather than production use. Notably, the release notes themselves do not enumerate individual changes; instead, they direct readers to the changelog files for the authoritative record of what shipped.
Per the release page, the tracking works differently for pre-releases than for stable versions:
- For stable releases, developers should refer to
CHANGELOG.mdat the repository root for details. - For pre-releases such as
v3.6.0-rc.9, the relevant details live in theCHANGELOG.mdof the minor branch (the3.6line) rather than the main stable changelog. - The release is published as a release candidate (
rc), signaling that the 3.6.0 feature set is being finalized but is not yet declared stable.
Because the tag carries no inline change list, the practical way to audit what moved between rc.8 and rc.9 is to diff the minor-branch changelog or inspect the commit range on GitHub. That keeps a single source of truth for the release train instead of duplicating notes per tag.
Why this matters to developers: 3.6 is a significant minor line, and each release candidate is a checkpoint where regressions are cheapest to catch. Teams running Vite-based apps, component libraries, or SSR setups should install the candidate in a staging environment using an explicit version pin, for example npm install [email protected], then run their test suites and report issues upstream. Pinning the exact rc version avoids silently upgrading to a later candidate, and reviewing the minor branch changelog before upgrading tells you whether a fix you are waiting on has actually landed.
Source: https://github.com/vuejs/core/releases/tag/v3.6.0-rc.9