Vue has published v3.5.43, a new stable release on the 3.5 line of the core framework. The GitHub release page itself is deliberately spartan: rather than duplicating notes, the team points readers to the canonical changelog. For stable releases, the guidance is to consult CHANGELOG.md in the repository, while pre-releases are documented in the CHANGELOG.md of the corresponding minor branch. That convention means the authoritative list of commits, fixes, and dependency bumps for v3.5.43 lives in the repo history, not in the release body.
What developers can take from the release metadata:
- v3.5.43 is a stable release, not a pre-release, so it is intended for production use on the
3.5line rather than as an early preview of the next minor. - Stable-release details are routed to the root
CHANGELOG.md; pre-release details are routed to the changelog maintained on the minor branch covering that series. - The tag is published from the
vuejs/corerepository athttps://github.com/vuejs/core/releases/tag/v3.5.43. - Because no per-release notes are embedded, verifying the exact fixes requires diffing the tag against the previous
3.5.xrelease or reading the changelog entries directly.
The practical implication for teams is upgrade discipline. Patch releases such as v3.5.43 are the low-risk lane for staying current: they typically carry bug fixes and small internal corrections while preserving the public API of the 3.5 series. If you pin dependencies, bump to [email protected] with your package manager and re-run your test suite; if you consume pre-releases, track the minor branch's changelog instead, since that is where the team documents unreleased behavior. Either way, treat the repository changelog as the source of truth before shipping an upgrade.