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
I know that recent versions of LiquidJS have introduced significant performance improvements. However, none of these upgraded dependancies are slated to be merged into the project until it reaches v1.0. While breaking changes should of course be avoided, this project is still in v0.x, and such changes are permitted by Semver:
Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.
— Semver specification, #4
Given the significance of the number 11 to this project, maybe the v0.11 release can introduce the above upgrades, whether these be in addition to other breaking changes or not.
The text was updated successfully, but these errors were encountered:
1.0 will be the next release after 0.11 and we’ll bundle these changes there. We’ll stick to strict semver for this project—I hate the exceptions to semver that exist for 0.x. We’ll get rid of the ambiguity there and make that explicit with a 1.0 jump.
A number of template projects 11ty includes have released major updates since this project began:
I know that recent versions of LiquidJS have introduced significant performance improvements. However, none of these upgraded dependancies are slated to be merged into the project until it reaches v1.0. While breaking changes should of course be avoided, this project is still in v0.x, and such changes are permitted by Semver:
Given the significance of the number 11 to this project, maybe the v0.11 release can introduce the above upgrades, whether these be in addition to other breaking changes or not.
The text was updated successfully, but these errors were encountered: