The Vue core team has published v3.6.0-rc.8, tagged in the vuejs/core repository as another release candidate in the run-up to the stable 3.6 release. As an rc build, it is a pre-release rather than a production-ready version, and the release notes point developers to the changelog rather than restating the diff inline. The guidance is explicit: for stable releases, refer to CHANGELOG.md; for pre-releases, refer to the CHANGELOG.md of the minor branch — in this case the minor branch tracking the 3.6 line.
Concrete details from the release:
- Tag: v3.6.0-rc.8, published on the
vuejs/coreGitHub releases page. - Version type: a pre-release (
rc) build, not a stable 3.6.0. - Changelog pointer: stable changes live in the root
CHANGELOG.md; pre-release changes live in theCHANGELOG.mdof the minor branch. - No individual commits, fixes or feature notes are enumerated in the release excerpt itself — the changelog files are the authoritative source.
- The release URL is the canonical reference for the tag:
https://github.com/vuejs/core/releases/tag/v3.6.0-rc.8.
For developers, rc releases are the testing window before a minor version is frozen. If you use Vue in a library, app or Nuxt project, this is the point to install the candidate, run your test suite and check for regressions, particularly around any APIs touched by the 3.6 work. Because the release notes defer to the minor branch CHANGELOG.md, the practical workflow is to read that file, compare it against your dependency constraints, and only pin v3.6.0-rc.8 in non-production environments until 3.6.0 ships as stable. Reporting issues against the tag while it is still a candidate gives the team the best chance to land fixes before the final release.
Source: https://github.com/vuejs/core/releases/tag/v3.6.0-rc.8