Skip to content

Bump to pyo3 0.25 #41

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

Merged
merged 2 commits into from
May 14, 2025
Merged

Bump to pyo3 0.25 #41

merged 2 commits into from
May 14, 2025

Conversation

kylebarron
Copy link
Contributor

Thank you for contributing to pyo3-async-runtimes!

Please consider adding the following to your pull request:

  • an entry in CHANGELOG.md
  • docs to all new functions and / or detail in the guide
  • tests for all new or changed functions

Be aware the CI pipeline will check your pull request for the following:

  • Rust tests (Just cargo test)
  • Rust lints (make clippy)
  • Rust formatting (cargo fmt)
  • Python formatting (black . --check. You can install black with pip install black)

@cjdsellers
Copy link
Collaborator

Thanks @kylebarron 🙏

@cjdsellers cjdsellers merged commit 23d6024 into PyO3:main May 14, 2025
32 checks passed
@kylebarron
Copy link
Contributor Author

Would you be able to push a new release?

@cjdsellers
Copy link
Collaborator

@kylebarron — sure! I’ll sync with @davidhewitt first to confirm the release procedure and any other considerations.

@jessekrubin
Copy link

@kylebarron saves the day!

@cjdsellers
Copy link
Collaborator

It looks like @davidhewitt is the crate owner, so I don't have a token to be able to publish.

I think we're also manually git-tagging and pushing a release: 0.25 commit at the same time?

I’ll stand by for confirmation.

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

Successfully merging this pull request may close these issues.

3 participants