Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Mar 23, 2025

This PR is a preview of the release that release-plan has prepared. To release you should just merge this PR 👍


Release (2025-06-16)

  • @glint/core 2.0.0-alpha.1 (major)
  • @glint/environment-ember-loose 2.0.0-alpha.1 (major)
  • @glint/environment-ember-template-imports 2.0.0-alpha.1 (major)
  • @glint/template 1.6.0-alpha.0 (major)
  • @glint/tsserver-plugin 2.0.0-alpha.1 (major)
  • @glint/type-test 2.0.0-alpha.1 (patch)

💥 Breaking Change

  • @glint/core, @glint/environment-ember-loose, @glint/environment-ember-template-imports, @glint/template
  • @glint/core, @glint/tsserver-plugin
    • #811 Migrate tests to TS Plugin mode, remove option for old LS mode (@machty)
  • Other
    • #790 Re-write extension to use reactive-vscode, align with Vue extension (@machty)
  • @glint/core
  • @glint/environment-ember-loose
    • #721 feat: drop support for classic component layout (@aklkv)
  • @glint/core, @glint/environment-ember-loose, @glint/environment-ember-template-imports
    • #726 Re-write using Volar: initially only supporting .gts (@machty)
  • @glint/core, @glint/template

🚀 Enhancement

  • Other
    • #895 VSCode: Add activationEvents for glimmer-ts/js file types (@machty)
    • #803 Use jiti for sync loading from TS Plugin (@machty)
    • #791 Monkeypatch remaining TS features within .gts files (@machty)
  • @glint/core, @glint/tsserver-plugin
    • #890 Move .gts/.gjs import hacks to TS Plugin (@machty)
    • #877 Reinstate GJS Support (@machty)
    • #873 Disregard semantic classification tokens from <template> portions of .gts files (@machty)
  • @glint/core
    • #888 Restore previous approach to glint-* directives atop new TS Plugin architecture (@machty)
    • #876 Support for Symbols, Outline, Code Folding in .gts files (@machty)
    • #874 Fix organize imports (@machty)
    • #856 Support (neo)vim filetypes for gts and gjs (@NullVoxPopuli)
    • #854 Loose mode: only parse .ts in components/ folder (@machty)
    • #838 Support extending multiple config files (@mogstad)
    • #839 use more specific nodes for open tag (@patricklx)
    • #813 Cleanup old LS remainders, disable CLI tests for now, rm ephemeral tests (@machty)
    • #749 Primitives for supporting ember-loose mode (.ts + .hbs) (@machty)
    • #747 volar-2.4.0-alpha.14 (@machty)
    • #713 check if template is in heritage clause (@patricklx)
  • @glint/core, @glint/template, @glint/tsserver-plugin
  • @glint/core, @glint/environment-ember-loose, @glint/environment-ember-template-imports, @glint/template
    • #753 TS Plugin: basic diagnostics and functionality for .gts files (@machty)
  • @glint/core, @glint/environment-ember-loose, @glint/environment-ember-template-imports
    • #726 Re-write using Volar: initially only supporting .gts (@machty)

🐛 Bug Fix

  • @glint/template
  • @glint/core, @glint/tsserver-plugin
    • #889 Reinstate "unused @glint-expect-error directive" (@machty)
  • @glint/core
    • #865 Prefer variables in scope over global variables (@mogstad)
    • #861 Inject hidden imports to fix .gts/.gjs extensions (@machty)
    • #851 Refrain creating ember-loose virtual code in non ember-loose environment (@mogstad)
    • #809 Bump volar to 2.4.12, fix caching issue w loose mode (@machty)
    • #799 Reinstate glint-expect-error (and other directives) for tsc and TS Plugin using Vue's approach (@machty)
    • #795 Restore "unused glint-expect-error" diagnostic (@machty)
    • #794 Reinstate expect-error directives for .gts (@machty)
    • #783 Suppress exception thrown by require.resolve if the file does not exist (@iarroyo)
    • #782 Typed ember/resolve config from extends package (@iarroyo)
    • #779 Closes #778 - add missing dependency to @glint/core (@NullVoxPopuli)
  • Other
  • @glint/environment-ember-template-imports
  • @glint/core, @glint/environment-ember-template-imports
  • @glint/tsserver-plugin
  • @glint/environment-ember-loose

📝 Documentation

🏠 Internal

Committers: 12

@github-actions github-actions bot added the internal Changes that don't impact the published packages label Mar 23, 2025
Copy link
Contributor

@NullVoxPopuli NullVoxPopuli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[NOT READY FOR MERGE]

(as of 2025-03-23)

We don't want @glint/template to release as a major version bump.

I don't think any meaningful changes have actually happened within it, but it probably got caught up in wide-sweeping changes that are breaking in the same PR.

When we're ready to release, we'll need to hand-edit the .release-plan.json and @glint/template/package.json to change the version bump to be a minor release.

@NullVoxPopuli
Copy link
Contributor

oh actually, it is breaking. because we dropped support for GlimmerX and formal support for DT Types.

HMMM. projects that already include @glint/template @ v1, may need to use an override to move to v2, as @glint/template has things that will not allow a second copy to exist and be compatible with @glint/core (the brand/symbol types, specifically)

@patricklx
Copy link
Contributor

patricklx commented Mar 23, 2025

Also, ts-plugin-test-app needs to be private
@NullVoxPopuli

@NullVoxPopuli
Copy link
Contributor

fixed @patricklx 🎉

@github-actions github-actions bot force-pushed the release-preview branch 17 times, most recently from 76a7b0a to 4008d7a Compare March 28, 2025 21:41
@github-actions github-actions bot force-pushed the release-preview branch 6 times, most recently from dd8f645 to 1a655bc Compare April 2, 2025 15:17
@github-actions github-actions bot force-pushed the release-preview branch 4 times, most recently from f62ea84 to 40cb70d Compare April 7, 2025 02:54
@github-actions github-actions bot force-pushed the release-preview branch 10 times, most recently from 7b64361 to 891a959 Compare April 16, 2025 17:54
@github-actions github-actions bot force-pushed the release-preview branch from 891a959 to fd4daa4 Compare May 7, 2025 21:33
Copy link
Contributor

@NullVoxPopuli NullVoxPopuli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re: declared "breaking" changes in @glint/template

So, I'm going to manually tell @glint/template to be a patch release, rather than a major (it's declared as a major due to basically re-writing Glint, which resulted in some sloppy git practices).

However!!!!
Here is a test of @glint/template@unstable (tracking every main commit) against a project that was previously using @glint/template@^1.5: universal-ember/ember-primitives#491

It's currently failing. Which means "something" did break something. We need to fix this, because we don't want to release a major of @glint/template, ideally -- since many packages depend on it -- we don't want to force a release that expands their version range to || ^2.0.0-alpha.0 if we don't have to.

In particular, it looks like our element subclassing is failing?

src/components/keys.gts:34:51 - error TS2345: Argument of type 'HTMLSpanElement' is not assignable to parameter of type 'HTMLElement'.
  Types of property '[GlintSymbol]' are incompatible.
    Type '"HTMLSpanElement"' is not assignable to type '"HTMLElement"'.

 34   <span class="ember-primitives__key-combination" ...attributes>

and

src/components/menu.gts:175:7 - error TS2345: Argument of type 'HTMLDivElement' is not assignable to parameter of type 'HTMLElement'.
  Types of property '[GlintSymbol]' are incompatible.
    Type '"HTMLDivElement"' is not assignable to type '"HTMLElement"'.

175       {{installContent isOpen=@isOpen triggerElement=@triggerElement}}
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

where this modifier has specified HTMLElement, and the element that the modifier is on is a HTMLDivElement. This should be allowed because HTMLElement is saying "I take any HTML".

@mansona
Copy link

mansona commented Jun 16, 2025

shouldn't @glint/template also be a pre-release here?

@NullVoxPopuli
Copy link
Contributor

Template has a bug which is blocking any releasing right now

#833 (review)

See: #903

There is some discussion in discord about this, too, iirc

@github-actions github-actions bot force-pushed the release-preview branch 2 times, most recently from 3e0d833 to d9e0fe5 Compare June 16, 2025 23:40
@NullVoxPopuli
Copy link
Contributor

Thanks to @mansona, our alpha versions look good.

All publishable packages will be alpha as of the merge of this PR.

The goal:

  • @glint/template should be compatible with all existing code, and the new glint (it's just types, and not related exactly to the language server stuff)
  • Test out the other @glint/* packages for the next-gen / v2 glint stuff, which is Volar powered

@NullVoxPopuli NullVoxPopuli merged commit 214df84 into main Jun 16, 2025
2 checks passed
@NullVoxPopuli NullVoxPopuli deleted the release-preview branch June 16, 2025 23:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal Changes that don't impact the published packages

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[volar] implicit dependency on vscode-languageserver-protocol leads to server boot errors

4 participants