Release the next version of rust-bindgen#3210
Closed
chotchki wants to merge 3 commits intorust-lang:mainfrom
Closed
Release the next version of rust-bindgen#3210chotchki wants to merge 3 commits intorust-lang:mainfrom
chotchki wants to merge 3 commits intorust-lang:mainfrom
Conversation
…ons. This is due to the 20.04 image being deprecated / removed as of 2025-04-15. actions/runner-images#11101
Author
|
So there are two issues here that I'm debating how to proceed on:
|
Contributor
|
Just published 0.72.0 |
Contributor
|
(Thanks for the digging in any case! The ubuntu builders we removed, but it still failed so I had to manually publish to crates.io) |
This file contains hidden or 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
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.
Based on my reading of https://github.com/rust-lang/rust-bindgen/blob/main/CONTRIBUTING.md#cutting-a-new-bindgen-release. I ran cargo release to bump rust-bindgen for a release. The steps do require a tag to be pushed as well and I don't think that can be done via pull request.
Reading through the changes merged to main, I think at least a semvar minor release is in order.
This is intended to help resolve issue: #3199 which is breaking bevy iOS simulator builds.