Skip to content

version bump #233

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Aug 22, 2023
Merged

Conversation

michaelraczycki
Copy link
Collaborator

0.0.10 -> 0.0.11

@ricardoV94
Copy link
Member

I don't remember if we need to bump twice in case we already did a release and added the 0.11 tag like it happened now

@michaelraczycki
Copy link
Collaborator Author

I think I can just manually re-run the workflows after merging, and it should release to pypi

@ricardoV94
Copy link
Member

I think I can just manually re-run the workflows after merging, and it should release to pypi

The version tag will not coincide with the right commit (this one), no?

@michaelraczycki
Copy link
Collaborator Author

if that will turn out to be blocking for the release, I'd just delete the 0.0.11 (since it has only my bug fix) and release 0.0.11 again

@ricardoV94
Copy link
Member

You can do that. You still have to delete the tag in the main branch: https://devconnected.com/how-to-delete-local-and-remote-tags-on-git/

@michaelraczycki michaelraczycki merged commit fc6e7ba into pymc-devs:main Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants