-
Notifications
You must be signed in to change notification settings - Fork 73
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
chore(main): release gyp-next 0.17.0 #232
chore(main): release gyp-next 0.17.0 #232
Conversation
@@ -1,5 +1,78 @@ | |||
# Changelog | |||
|
|||
## [0.17.0](https://github.com/nodejs/gyp-next/compare/gyp-next-v0.16.2...gyp-next-v0.17.0) (2024-03-11) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like something's wrong in the config. Tags shouldn't include the package's name.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/cc @lukekarrys
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Legacy Python 2 was dropped in https://github.com/nodejs/gyp-next/releases/tag/v0.8.0 so I do not think we should highlight that in the release!
It looks like it didn't correctly find the most recent release. I will make a new PR that uses the I will also add a config to fix the tag names. |
🤖 I have created a release beep boop
0.17.0 (2024-03-11)
⚠ BREAKING CHANGES
gyp
Features
gyp --version
(#164) (5c9f4d0)Bug Fixes
Documentation
This PR was generated with Release Please. See documentation.