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

chore(main): release 0.18.1 #258

Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented May 12, 2024

🤖 I have created a release beep boop

0.18.1 (2024-05-26)

Bug Fixes

  • ci: add Python 3.13 pre-release to test matrix (#257) (8597203)

Documentation


This PR was generated with Release Please. See documentation.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--gyp-next branch from dc32b18 to 3612896 Compare May 23, 2024 14:16
@legendecas
Copy link
Member

legendecas commented May 24, 2024

I would like this to be released with #248.

Also, this is blocked with #256.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--gyp-next branch from 3612896 to 3c43a24 Compare May 24, 2024 12:39
@github-actions github-actions bot force-pushed the release-please--branches--main--components--gyp-next branch from 3c43a24 to 980db33 Compare May 26, 2024 12:09
@legendecas
Copy link
Member

Let's see if the release automation works.

@legendecas legendecas merged commit bf43efb into main May 29, 2024
@legendecas legendecas deleted the release-please--branches--main--components--gyp-next branch May 29, 2024 09:18
Copy link
Contributor Author

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

@legendecas
Copy link
Member

Release is at https://pypi.org/project/gyp-next/0.18.1/ as well!

@legendecas
Copy link
Member

Verified that pipx run gyp-next with --help and --version now both works.

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