release: 0.20.1 #3713
Merged
release: 0.20.1 #3713
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 3 to 4. - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@v3...v4) --- updated-dependencies: - dependency-name: actions/setup-node dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: Niko Matsakis <niko@alum.mit.edu>
Co-authored-by: Bruno Kolenbrander <59372212+mejrs@users.noreply.github.com>
This is necessary for async functions
In pyca/cryptography this function is the #1 source of lines of generated LLVM IR, because it is duplicated 42x (and growing!). By rewriting it so most of the logic is monomorphic, we reduce the generated LLVM IR for this function by 4x.
Closes #3615 This simply adds a new method which uses the existence of a `PyVisit` object as proof that the GIL is held instead of a `Python` object. This allows `GILProtected` to be used in instances where contained Python objects need to participate in garbage collection. Usage in this situation should be valid since no Python calls are made and this does not provide any additional mechanism for accessing a `Python` object.
davidhewitt
added
CI-no-fail-fast
|
I'm pretty certain that I'm going to have to fight CI, though with luck I picked all the necessary commits 🙈 |
|
Assuming CI is green and I hear no concerns, I'll aim to put this live tomorrow evening. |
davidhewitt
force-pushed
the
release-0.20.1
branch
from
eb164d2 to
d3f034a
Compare
|
Release is live! |
|
Thanks a lot for your work! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a patch release which picks various docs additions, some minor nonbreaking additions, and also a few fixes as 0.20.1.
I'd sort of hoped we wouldn't need to do this, but unfortunately we had the clippy warning in #3561 which is now stable in Rust 1.75. I think 0.21 is still a couple weeks away, so I think the ecosystem can benefit from having this pushed sooner.
Fixes rust-lang/rust-clippy#12039