Skip to content

Prepare 0.18.1 release - #1653

Merged
IvanIsCoding merged 5 commits into
Qiskit:stable/0.18from
mtreinish:prepare-181
Jul 29, 2026
Merged

Prepare 0.18.1 release#1653
IvanIsCoding merged 5 commits into
Qiskit:stable/0.18from
mtreinish:prepare-181

Conversation

@mtreinish

Copy link
Copy Markdown
Member

We've collected a fair number of bugfixes on top of 0.18.0 that would be good to release. This commit prepares for tagging a 0.18.1 release by bumping the version numbers and adding a prelude release note. Once this merges it should be tagged as 0.18.1.

We've collected a fair number of bugfixes on top of 0.18.0 that would be
good to release. This commit prepares for tagging a 0.18.1 release by
bumping the version numbers and adding a prelude release note. Once this
merges it should be tagged as 0.18.1.

@IvanIsCoding IvanIsCoding left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is good to go, we do need to move some release notes but we have accumulated enough small things that it is worth releasing.

With that being said, I am going to be biased and say "can we try including this":

  1. #1643, this closes #1639 and it's a trivial amount of work,
  2. #1620, this is less trivial but it will let us stop depending on pyodide-recipes (pyodide/pyodide-recipes#599).

@mergify

mergify Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

  • Queue this pull request

@IvanIsCoding

IvanIsCoding commented Jul 26, 2026

Copy link
Copy Markdown
Collaborator

Also, I fixed it the public docs via a manual commit but:

release = '0.17.1'

Let's update the docs version, we forgot about that in 0.18.0. I will send a PR to avoid that kind of mistake in the future

edit: or alternatively just merge #1655 and backport. that works too.

@IvanIsCoding

Copy link
Copy Markdown
Collaborator

Flagging from https://github.com/Qiskit/rustworkx/actions/runs/30454648607/job/90585000226

GCC from our pinned cibuildwheel is clashing with NumPy?! For some reason we are building NumPy from source and it’s failing for x86-64

@mtreinish

mtreinish commented Jul 29, 2026

Copy link
Copy Markdown
Member Author

It's the use of manylinux 2014. Modern numpy wheels are built on manylinux 2_27 which is obviously not compatible with the manylinux 2010, so pip is trying to build it from source. But the gcc version we have in the manylinux container is too old now too so that fails. We should be able to set the --prefer-binary flag on the test install step so that it will just skip the newer versions of numpy that don't have manylinux compatible wheels. Where we'll have trouble is with newer python versions that don't have any wheels on a compatible manylinux tag. Obviously numpy 2.4.6 worked though since we could release 0.18.0 (before numpy 2.5.0 was released) so maybe we just pin to numpy < 2.5 in cibuildwheel for right now and look at bumping our manylinux version in 0.19.0.

@coveralls

Copy link
Copy Markdown

Coverage Report for CI Build 30492523303

Coverage remained the same at 94.689%

Details

  • Coverage remained the same as the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 20296
Covered Lines: 19218
Line Coverage: 94.69%
Coverage Strength: 926817.93 hits per line

💛 - Coveralls

@IvanIsCoding

Copy link
Copy Markdown
Collaborator

For sanity, I ran another dry-run on my fork: https://github.com/IvanIsCoding/rustworkx/actions/runs/30496390043/job/90726120705

I think this is good to go.

@IvanIsCoding
IvanIsCoding merged commit 736a1bc into Qiskit:stable/0.18 Jul 29, 2026
69 of 73 checks passed
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