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

Allow @glimmer/component v2 #530

Merged
merged 8 commits into from
Nov 12, 2024
Merged

Allow @glimmer/component v2 #530

merged 8 commits into from
Nov 12, 2024

Conversation

mkszepp
Copy link
Collaborator

@mkszepp mkszepp commented Nov 11, 2024

No description provided.

@mkszepp mkszepp merged commit 6f5119e into master Nov 12, 2024
19 checks passed
@mkszepp mkszepp deleted the allow-glimmer-component-v2 branch November 12, 2024 06:34
@@ -55,5 +55,6 @@
},
"npm": false
},
"version": "1.2.0"
"version": "1.2.0",
"packageManager": "pnpm@9.12.3+sha512.cce0f9de9c5a7c95bef944169cc5dfe8741abfb145078c0d508b868056848a87c81e626246cb60967cbd7fd29a6c062ef73ff840d96b3c86c40ac92cf4a813ee"
Copy link
Contributor

Choose a reason for hiding this comment

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

was this put here intentionally?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

upps... yes... forget to move to npm v18... thanks for hint

Copy link
Collaborator Author

@mkszepp mkszepp Nov 12, 2024

Choose a reason for hiding this comment

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

when everything works fine we will move everything in next time to node 20 & pnpm 9 (not after current release)

@mkszepp
Copy link
Collaborator Author

mkszepp commented Nov 12, 2024

@Techn1x published in v1.3.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants