Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce breaking (template language) changes in v0.11.0 #1091

Closed
paulrobertlloyd opened this issue Apr 12, 2020 · 2 comments
Closed

Introduce breaking (template language) changes in v0.11.0 #1091

paulrobertlloyd opened this issue Apr 12, 2020 · 2 comments

Comments

@paulrobertlloyd
Copy link
Contributor

A number of template projects 11ty includes have released major updates since this project began:

Language 11ty version Latest version
Mustache (#371) 2.3.2 3.1.0
LiquidJS (#469) 6.4.3 9.11.10
markdown-it (#669) 8.4.2 10.0.0

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.

@zachleat
Copy link
Member

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.

@zachleat zachleat added this to the Eleventy v1.0.0 milestone Apr 20, 2020
@zachleat zachleat added this to Needs triage in Eleventy 1.0 via automation Apr 20, 2020
@zachleat zachleat modified the milestones: Planning for Eleventy v1.0.0, Eleventy 1.0.0 Aug 11, 2020
@zachleat zachleat moved this from Needs triage to Closed in Eleventy 1.0 Aug 11, 2020
@zachleat
Copy link
Member

Closing this as 1.0 development has commenced and we have individual issues for each of these.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Eleventy 1.0
  
Closed
Development

No branches or pull requests

2 participants