-
Notifications
You must be signed in to change notification settings - Fork 36
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
🐛 Bug: Upgrading Node to verison 18 broke builds #92
Comments
+1 It would be greatly appreciated if you could please create a |
+1 Can you please create the tag |
## PR Checklist - [x] Addresses an existing open issue: fixes #92 - [x] That issue was marked as [`status: accepting prs`](https://github.com/dmnd/dedent/issues?q=is%3Aopen+is%3Aissue+label%3A%22status%3A+accepting+prs%22) - [x] Steps in [CONTRIBUTING.md](https://github.com/dmnd/dedent/blob/main/.github/CONTRIBUTING.md) were taken ## Overview Removes the requirements so they don't impact users.
Sorry about that folks! I published |
🎉 This is included in version v1.5.3 🎉 The release is available on: Cheers! 📦🚀 |
Thank you for the quick fix @JoshuaKGoldberg !! |
Bug Report Checklist
main
branch of the repository.Expected
A major node version dependency should not be upgraded in a bug fix.
Actual
NPM is showing the latest version is
1.5.2
, which requires Node18
. This is breaking our application since Jest29.5.0
has this somewhere in the dependency tree only supporting Node16
.Additional Info
It looks like that tag was removed from GitHub. A new tag that reverts functionality back to
1.5.1
should be tagged as1.5.3
.The text was updated successfully, but these errors were encountered: