Skip to content

chore(main): release 0.18.0#253

Merged
cclauss merged 1 commit into
mainfrom
release-please--branches--main--components--gyp-next
May 8, 2024
Merged

chore(main): release 0.18.0#253
cclauss merged 1 commit into
mainfrom
release-please--branches--main--components--gyp-next

Conversation

@github-actions

@github-actions github-actions Bot commented May 8, 2024

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.18.0 (2024-05-08)

Features

  • support language standard keys in msvs_settings (#252) (322f6d5)

This PR was generated with Release Please. See documentation.

@legendecas

Copy link
Copy Markdown
Member

I think we should make a release soon to fix pipx issue. Any concerns?

@cclauss

cclauss commented May 8, 2024

Copy link
Copy Markdown
Contributor

It would be good to land this but it would be good to get Node.js v22 passing on Windows in

Ready to go...

@cclauss cclauss merged commit 0fdb0ec into main May 8, 2024
@cclauss cclauss deleted the release-please--branches--main--components--gyp-next branch May 8, 2024 13:04
@github-actions

github-actions Bot commented May 8, 2024

Copy link
Copy Markdown
Contributor Author

🤖 Release is at https://github.com/nodejs/gyp-next/releases/tag/v0.18.0 🌻

@cclauss

cclauss commented May 8, 2024

Copy link
Copy Markdown
Contributor

https://github.com/nodejs/gyp-next/releases is v0.18.0
https://pypi.org/project/gyp-next is v0.17.0

What steps are required to ship to PyPI?

@legendecas

Copy link
Copy Markdown
Member

I plan to publish manually this time as well. Going to continue polishing #248 so that the next version could be published by automation.

@legendecas

legendecas commented May 8, 2024

Copy link
Copy Markdown
Member

Published https://pypi.org/project/gyp-next/0.18.0/.

pipx run --no-cache --index-url https://pypi.org/simple gyp-next==0.18.0 --help now works.

@cclauss

cclauss commented May 8, 2024

Copy link
Copy Markdown
Contributor

gyp --help on Py3.12 now works but gyp --version fails. I will dig in.

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