All pre-releases are considered unstable and may ship breaking changes in between, so always pin to exact versions when using pre-releases. Pre-releases are meant for integration / stability testing, and for early adopters to provide feedback for unstable features. You can install them via npx or npx respectively. They are published as different packages to avoid bloating the npm metadata of the stable channel. Major releases will go through an alpha phase and a beta phase.Īdditionally, we publish canary releases every week from the main and minor branches on GitHub. Minor releases typically go through a non-fixed number of beta releases. As a result, your package may need to explicitly declare a minimum required minor version of Vue. A version mismatch can only happen if you ship pre-compiled Vue component code as a package, and a consumer uses it in a project using an older version of Vue. This is only a concern for library authors, because in applications, the compiler version and the runtime version is always the same. For example, code generated by Vue 3.2 compiler may not be fully compatible if consumed by the runtime from Vue 3.1. Compiled Code Compatibility with Older Runtime Ī newer minor version of Vue compiler may generate code that isn't compatible with the Vue runtime from an older minor version. If you are using TypeScript, you can use a semver range that locks the current minor and manually upgrade when a new minor version of Vue is released. Occasionally we may need to adopt features that are only available in a newer version of TypeScript, raising the minimum required version of TypeScript. Sometimes TypeScript itself ships incompatible changes between minor versions, and we may have to adjust types to support newer versions of TypeScript. We may ship incompatible changes to TypeScript definitions between minor versions. Vue releases follow Semantic Versioning with a few edge cases. Major releases will be announced ahead of time, and will go through an early discussion phase and alpha / beta pre-release phases. Minor releases always go through a beta pre-release phase. Minor releases always contain new features, with a typical time frame of 3~6 months in between. A full changelog of past releases is available on GitHub.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |