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

Plan v5 Release #2319

Closed
bmish opened this issue Jan 5, 2022 · 11 comments · Fixed by #2670
Closed

Plan v5 Release #2319

bmish opened this issue Jan 5, 2022 · 11 comments · Fixed by #2670
Assignees
Labels
Milestone

Comments

@bmish
Copy link
Member

bmish commented Jan 5, 2022

Planned changes for v5

Done already?

Future changes not yet ready:

Follow-up tasks:

For reference, v4.0.0 was released 2022-01-05, discussion in #1908.

v5 Preparation PR: #2670

Pre-release versions:

@bmish bmish added the breaking label Jan 5, 2022
@NullVoxPopuli
Copy link
Contributor

when are you wanting to release v5?

@bmish
Copy link
Member Author

bmish commented Jan 6, 2022

Mid-2022 so we can drop support for Node versions that will end-of-life around then, assuming we have enough breaking changes compiled.

@bmish bmish added this to the 5.0.0 milestone Feb 25, 2022
@scalvert
Copy link
Member

I've dropped Node 12 support in my PR unifying the bin testing infra (#2437). It's required, since the bin-tester package requires Node 14+. We can merge it into a next branch if we want, but I'm concerned that it'll be hard to merge with master once we're ready to release.

@bmish
Copy link
Member Author

bmish commented Apr 12, 2022

I would prefer we have a separate PR for each breaking change. That way, we have smaller, simpler PRs and each change will show up nicely as a separate item in the changelog. I think the next branch could be appropriate to begin if you'd like to.

@scalvert
Copy link
Member

I would also prefer this and am happy to port the change to a separate PR. We should definitely update next with master to start pulling in changes for v5.

@bmish
Copy link
Member Author

bmish commented Sep 1, 2022

I would like to start preparing for this release soon. Any other breaking changes we should include? The current list has some straightforward rule / config changes but also some more complex behavior changes that need to be implemented.

@NullVoxPopuli
Copy link
Contributor

NullVoxPopuli commented Sep 1, 2022

can we include #2601 ?

gts/gjs is already very easy to use in apps / v1 addons, and it'd be great if we got linting enabled by default
we'd probably also want to recommend disabling some rules for tests/**/* -- which ELS already checks, but the CLI doesn't (but this change would enable the CLI to check tests).

Tests can use <template>, just like everywhere else, I have examples of this here: https://github.com/NullVoxPopuli/ember-resources/blob/main/testing/ember-app/tests/core/rendering-test.gts
and when linting those, it also makes sense to lint hbs backticks, which I believe is the proposal

@bmish
Copy link
Member Author

bmish commented Nov 3, 2022

First alpha release of v5 published! Please test it out and let us know if you want to include additional breaking changes before the final release in a week or two

https://github.com/ember-template-lint/ember-template-lint/releases/tag/v5.0.0-alpha.0

@bmish
Copy link
Member Author

bmish commented Nov 15, 2022

Status:

@rwjblue
Copy link
Member

rwjblue commented Nov 17, 2022

@bmish just landed #2696 thanks for pinging!

@bmish
Copy link
Member Author

bmish commented Nov 19, 2022

Release completed: https://github.com/ember-template-lint/ember-template-lint/releases/tag/v5.0.0

@bmish bmish mentioned this issue Nov 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
4 participants