v6 release: the last major?

[NullVoxPopuli]

Remaining todos here #1568

(most of this is documentation tho, and non-breaking)

---

Keeping track of changes here for the changelog, tho it does seem like release-it is set up, so this'll all probably be automatic:

Breaking

• Use the current Node LTS #1570

Enhancements

• Loosen version check against ember-cli-babel #1569
• Adding note to testing.md about qunit-dom #1562
• docs: Reference Glint in docs #1554
• Update getOwner example #1546

Fixes

• fix: typo in code example in components.md #1560
• Fix ModelRegistry declaration example #1563
• chore: Fix spelling mistake #1538

Dependencies

• chore(deps): bump decode-uri-component from 0.2.0 to 0.2.2 #1542
• Remove deprecated @types/ember__test-helpers from blueprint #1545

[Polve]

I comment here to avoid opening a new ticket since I've a couple questions that seem vaguely related.

1. in the ember-cli-typescript documentation I read:

Ember makes heavy use of decorators, and TypeScript does not currently support deriving type information from decorators.

But in reading ts 5.2 release notes I see they've added support for decorator metadata: is that related and meaning that section will be obsolete in time?

2. I created a new ember typescript project (ember new prj --typescript) with ember-cli 5.3 and this addon is not installed by default: do I need to add it manually?

I apologize in advance if my questions are very dumb since I'm a total newbie in ember.

[chriskrycho]

@Polve good questions, but better served by opening a Discussion, so please move there! Thanks!

[Techn1x]

Would it be possible to release the loosened ember-cli-babel version check as a v5 patch rather than as part of the v6 major? Or too much work to split it out for little gain?

I ask because my application has dropped ember-cli-typescript, but I still see the message due to addon dependencies on ember-cli-typescript v5. I imagine those addons are probably not likely to update to v6 and are more likely to drop it instead (as they should). But if they do neither a patch version will mean consumers can at least get rid of the warning message without needing to use overrides/resolutions

[NullVoxPopuli]

I tried just.. getting CI passing.. and it's hard idk what incantations are needed atm. I'd (personally) prefer someone release current main (which already has the ec-babel fix, iirc) without trying to get CI green.

[Techn1x]

Are you able to lend aid @chriskrycho ?

Based on the opening comment, it seems like all the necessary changes have been made, we just need to get releases happening

[chasegiunta]

Also looking for a release here 👀