We upgrade our packages to a stable version for each 1.x.x.
The idea behind this is to mark the fact that Vitamin now considers itself stable and this is related to the decision to build a new, more modern, accessibility-aware, design token-based and right-to-left compatible implementation.
There is no breaking change, it's just a switch from version 0.x.x to 1.x.x.
Technically, with Lerna it is impossible to bump automatically from 0.x.x to 1.x.x via a simple commit message following conventional commits with "BREAKING CHANGE" because it is a 0.x.x and technically, it can break at each minor version change too, that's why this PR proposes to bumper manually all packages in 1.0.0. So they will once be merged PR create 1.1.0 releases on all of our packages @vtmn/xxx.
Thanks
Checklist
[x] Make sure you are requesting to pull a topic/feature/bugfix branch. Please, don't request directly from your main!
Changes description
We upgrade our packages to a stable version for each
1.x.x
. The idea behind this is to mark the fact that Vitamin now considers itself stable and this is related to the decision to build a new, more modern, accessibility-aware, design token-based and right-to-left compatible implementation.There is no breaking change, it's just a switch from version
0.x.x
to1.x.x
.Technically, with Lerna it is impossible to bump automatically from
0.x.x
to1.x.x
via a simple commit message following conventional commits with "BREAKING CHANGE" because it is a0.x.x
and technically, it can break at each minor version change too, that's why this PR proposes to bumper manually all packages in 1.0.0. So they will once be merged PR create 1.1.0 releases on all of our packages@vtmn/xxx
.Thanks
Checklist
design-system-core-team-design
GitHub team.Does this introduce a breaking change?