-
Notifications
You must be signed in to change notification settings - Fork 191
Comparing changes
Open a pull request
base repository: Qiskit/rustworkx
base: 0.13.0
head repository: Qiskit/rustworkx
compare: 0.13.1
- 9 commits
- 43 files changed
- 6 contributors
Commits on Jun 9, 2023
-
Sort the todo_nodes (#897) (#898)
(cherry picked from commit af4af62) Co-authored-by: Edwin Navarro <enavarro@comcast.net>
Configuration menu - View commit details
-
Copy full SHA for da5fd17 - Browse repository at this point
Copy the full SHA da5fd17View commit details
Commits on Jun 17, 2023
-
Apply wheel job fixes from 0.13.0 release (#896) (#904)
* Apply wheel job fixes from 0.13.0 release This commit applies the various fixes needed to the wheel publishing job definitions for the 0.13.0 release. There were several jon errors during the release which were caused by various changes made to rustworkx, upstream dependencies, and CI environment since the 0.12.0 which caused issues during the release process. #753 should still be finished to simplify the job definitions, but that should be rebased to take this more targeted fix. The intent is for this to be a minimal diff for backporting to stable/0.13 for a future 0.13.1 release. Of particular importance here though is the change in support tier for s390x from 3 to 4. This was caused by repeated issues with timeouts caused by running tests during the s390x linux wheel builds. To ensure we can reliably build the wheels this drops the testing from the s390x so that they can reliably complete in 12 job hours. * Fix docs * Update releasenotes/notes/s390x-tier-4-1701a0f044759cd1.yaml * Update releasenotes/notes/s390x-tier-4-1701a0f044759cd1.yaml Co-authored-by: Edwin Navarro <enavarro@comcast.net> --------- Co-authored-by: Edwin Navarro <enavarro@comcast.net> (cherry picked from commit 8720cd3) Co-authored-by: Matthew Treinish <mtreinish@kortar.org>
Configuration menu - View commit details
-
Copy full SHA for 2baaf11 - Browse repository at this point
Copy the full SHA 2baaf11View commit details
Commits on Jun 20, 2023
-
Pin Python version in CI (#905) (#906)
* Pin Python version in CI Recently github updated the cached version of python installed for 3.7 in the CI environment to 3.7.17. This new binary was not built with bz2 support which is causing failures in our CI jobs that run with 3.7. While we'll be dropping 3.7 support from the main branch (for 0.14.0) in the near future we still support 3.7 on the stable 0.13.x series. This commit pins the python version to the previous patch release which was known to work. * Use 3.7 on windows * Fix windows capitalization * Fix syntax error (cherry picked from commit 5f73e76) Co-authored-by: Matthew Treinish <mtreinish@kortar.org>
Configuration menu - View commit details
-
Copy full SHA for 283a663 - Browse repository at this point
Copy the full SHA 283a663View commit details
Commits on Jul 17, 2023
-
Adding Clippy Fix (backport #930) and Pin pillow<10 in CI (backport #922
) (#931) * Adding fix that clippy warns for (#930) Because of a new Rust update, Clippy now warned for a line of code in cycle_basis.rs in rustworkx-core. This PR fixes that one line so that Clippy passes. (cherry picked from commit d88f18b) * Pin pillow<10 in CI (#922) Since the recent release of Pillow 10.0.0 the docs CI job has started failing due to an error in Pillow when trying to run the jupyter-execute cell in the `.to_dot()` docstring. It looks like a bug that was introduced in the new release which is being tracked in python-pillow/Pillow#7259 where it's trying to return a jpeg representation of the object from the RGBA data loaded from a PNG. Until the issue is resolved upstream in pillow this commit just caps the version we run in CI via the constraints file. While pillow is an optional dependency and we could cap the version in the extras, this issue isn't severe enough to warrant that, and the typical pillow usage, especially via the rustworkx api (i.e. graphviz_draw() which returns a PIL.Image object) will continue to work as expected with pillow 10.0.0 there isn't a reason to cap more broadly. This is just needed as a workaround to unblock CI. --------- Co-authored-by: danielleodigie <97267313+danielleodigie@users.noreply.github.com> Co-authored-by: Matthew Treinish <mtreinish@kortar.org>
Configuration menu - View commit details
-
Copy full SHA for 14af315 - Browse repository at this point
Copy the full SHA 14af315View commit details
Commits on Jul 20, 2023
-
Relax constraints in rustworkx-core for hashbrown and indexmap (#929)
* Relax constraints in rustworkx-core for hashbrown and indexmap This commit updates the version constraints on the hashbrown and indexmap dependencies in rustworkx-core's dependency list. These 2 dependencies are used for I/O to rustworkx-core and we previously had our versions set to the highest version compatible with the msrv. However, for users of rustworkx-core with newer MSRVs this limited version support caused issues if they wanted to use a newer version of these library (which was compatible with their MSRV) as an input or output to rustworkx-core. For example, as described in #911 qiskit-terra was using hashbrown 0.13.x and had errors because the released version of rustworkx-core only was listed as compatible with hashbrown 0.12. This version mismatch meant that the hashbrown objects created in qiskit-terra were not recognized by rustworkx-core because of the version mismatch. This commit attempts to fix this issue by increasing the allowable range of versions to be greater than or equal to our previous fixed version and capped at the last known working version. This should enable users to set a fixed library version that they want even if it's newer and requires a higher MSRV. This commit is for the stable/0.13 branch as the minimum version is lower on the stable branch as the MSRV for the 0.13.0 is much older than what we're using on the main branch now. A separate PR will be pushed up for main to update it there. This was done in reverse in the interest of ensuring we include this in 0.13.1 and the inevitable backport conflict if we started with main first. Fixes #911 * Try manually setting package version in msrv ci job * Apply suggestions from code review --------- Co-authored-by: Ivan Carvalho <8753214+IvanIsCoding@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for f874efc - Browse repository at this point
Copy the full SHA f874efcView commit details
Commits on Jul 25, 2023
-
Reorganize API docs into subpages (#927) (#943)
* Reorganize API docs into subfolders * Increase maxdepth for functions page --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 4200d67 - Browse repository at this point
Copy the full SHA 4200d67View commit details -
Switch to Qiskit Ecosystem theme (#926) (#941)
* Upgrade to new Qiskit sphinx theme * Use ecosystem theme --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit e9b9c12) Co-authored-by: Eric Arellano <14852634+Eric-Arellano@users.noreply.github.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 2ba34e4 - Browse repository at this point
Copy the full SHA 2ba34e4View commit details
Commits on Jul 26, 2023
-
Add a section to Python docs about page for rustworkx-core (#944) (#945)
* Add a section to Python docs about page for rustworkx-core The main page explaining the rustworkx library in the Python docs previously didn't make any mention of rustworkx-core. While in general the Python side is built on top of rustworkx-core and the vast majority of the users of the Python library don't need to know about the pure Rust library inside, it is still good to highlight its existence in case anyone finds the Python library but is really interested in consuming it from Rust. This commit just adds a small subsection to the about page explaining the existence of rustworkx-core, its purpose, and where you can find mroe information about it. * Apply suggestions from code review Co-authored-by: Edwin Navarro <enavarro@comcast.net> --------- Co-authored-by: Edwin Navarro <enavarro@comcast.net> (cherry picked from commit 2a16d21) Co-authored-by: Matthew Treinish <mtreinish@kortar.org>
Configuration menu - View commit details
-
Copy full SHA for 69ab37f - Browse repository at this point
Copy the full SHA 69ab37fView commit details
Commits on Jul 29, 2023
-
* Prepare 0.13.1 release This commit prepares the 0.13.1 release, this consists of bumping the version number to 0.13.1 in all the appropriate files. It also adds a prelude release note to provide a brief introduction to the release. When this commit merges it should be tagged as the 0.13.1 release. Closes #893 * Add missing fix notes * Apply suggestions from code review Co-authored-by: Edwin Navarro <enavarro@comcast.net> --------- Co-authored-by: Edwin Navarro <enavarro@comcast.net>
Configuration menu - View commit details
-
Copy full SHA for a0bca3a - Browse repository at this point
Copy the full SHA a0bca3aView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 0.13.0...0.13.1