You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 2, 2026. It is now read-only.
Currently, all packages (core language, VS Code extension, IntelliJ plugin, and CLI) use the same version, meaning a package can have its version upgraded just because the language core got updated, but also that the extension/plugin/CLI cannot be updated without the core language being updated.
The versioning of the packages should ideally be independent, and there should be separate Changelogs and separate CI pipelines to release only the packages that have changed.
The question of when to make a release on GitHub remains. One way is to make a release for any update in any package and name it with the package name and version (which is followed by Svelte and Astro). Another way is to make one release for all packages at once, but that would probably mean using the same version number for all packages (which is what Vue does).
For the first way, the CI can be set to trigger on a tag that starts with the package name (created on release), as Svelte does.
Additionally, the respective packages should be published to NPM in the CI, if relevant.
Currently, all packages (core language, VS Code extension, IntelliJ plugin, and CLI) use the same version, meaning a package can have its version upgraded just because the language core got updated, but also that the extension/plugin/CLI cannot be updated without the core language being updated.
The versioning of the packages should ideally be independent, and there should be separate Changelogs and separate CI pipelines to release only the packages that have changed.
The question of when to make a release on GitHub remains. One way is to make a release for any update in any package and name it with the package name and version (which is followed by Svelte and Astro). Another way is to make one release for all packages at once, but that would probably mean using the same version number for all packages (which is what Vue does).
For the first way, the CI can be set to trigger on a tag that starts with the package name (created on release), as Svelte does.
Additionally, the respective packages should be published to NPM in the CI, if relevant.