Prepare 0.18.0 release#1607
Merged
Merged
Conversation
Collaborator
|
I will send a PR today to publish a 3.14t wheel. At least for Linux and macOS. Right now, there is a skip we will simply remove the skip. |
Collaborator
|
#1612 is under testing, I will update once I have confirmation our wheels action is healthy. Let's call it a dry-run |
IvanIsCoding
approved these changes
Jun 18, 2026
| and the documentation for the library is hosted here: | ||
|
|
||
| https://docs.rs/rustworkx-core/0.13.0/rustworkx_core/ | ||
| https://docs.rs/rustworkx-core/ |
Collaborator
There was a problem hiding this comment.
Nice catch, it is easier to have an URL that defaults to latest
This commit makes a few updates to the repository to prepare for the release of rustworkx 0.18.0. First it updates the version numbers to 0.18.0. It then reorganizes the release notes by moving the 0.18.0 note files into a separate directory, and updating them for syntax issues and clarity. A prelude release note is added to highlight the features of the release. As part of this a new subsection mechanism is added to the release notes to have a subsection for rustworkx-core features and upgrade notes. Finally, some small documentation fixes are made to reflect the current state of the project with this release. Mainly removing indirect references to support for Python versions older than 3.10, incorrectly documenting the EoL of the retworkx name as the pending 1.0 release, and stale instructions to manually install setuptools-rust if pip or your PEP-517 compliant builder doesn't.
Member
Author
|
I moved the new notes in e830930. I did a rebase and force push as reno sometimes struggles with a move with merge commits |
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
2 participants
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 commit makes a few updates to the repository to prepare for the release of rustworkx 0.18.0. First it updates the version numbers to 0.18.0. It then reorganizes the release notes by moving the 0.18.0 note files into a separate directory, and updating them for syntax issues and clarity. A prelude release note is added to highlight the features of the release. As part of this a new subsection mechanism is added to the release notes to have a subsection for rustworkx-core features and upgrade notes.
Finally, some small documentation fixes are made to reflect the current state of the project with this release. Mainly removing indirect references to support for Python versions older than 3.10, incorrectly documenting the EoL of the retworkx name as the pending 1.0 release, and stale instructions to manually install setuptools-rust if pip or your PEP-517 compliant builder doesn't.
This is on hold until the remaining 0.18 PRs merge. The current list of open PRs is:
Closes: #1529