Closed Andrew-S-Rosen closed 11 months ago
Hmm, that is indeed weird :thinking: . We'll look into this.
(btw, I believe you meant 0.230.0 instead of 0.223.0 here :sweat_smile: :
The CHANGELOG release versions are not compatible with the actual releases on PyPI. For instance, it says 0.223.0.rc0 was released on 2023-11-24 in the CHANGELOG, but that was actually 0.229.0.rc.0. )
What is up with me and numbers lately!! 😂😂😂
@Andrew-S-Rosen After a quick overview of the nightly workflow, it seems like this should be fixed now as there's a 230 release on pypi. It was actually that release on pypi that got out of sync/wrong. I believe things should function as expected from now as both are now at 230.
I'd vote for making this issue as resolved and if we encounter a similar scenario again, we can reopen it.
Ah, makes sense! Closing.
Environment
What is happening?
The CHANGELOG release versions are not compatible with the actual releases on PyPI. For instance, it says 0.230.0.rc0 was released on 2023-11-24 in the CHANGELOG, but that was actually 0.229.0.rc.0.
How can we reproduce the issue?
Look at the CHANGELOG :)
What should happen?
The versions should match.
Any suggestions?
Maybe I am bad at reading :)