Skip to content
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

No-change VERSION bump to 6.0.3 #347

Merged
merged 1 commit into from
Feb 20, 2024
Merged

Conversation

paride
Copy link
Collaborator

@paride paride commented Feb 20, 2024

I wasted version 1!6.0.2 while testing one previous PR, which required running jobs that normally only run when new commits land to the main branch. We can't just delete the tag and delete the release from pypi because pypi doesn't allow version reuse. Let's just bump VERSION yet another time.

I wasted version 1!6.0.2 while testing the previous PR, which required
running jobs that normally only run when new commits land to the main
branch. We can't just delete the tag and delete the release from pypi
because pypi doesn't allow version reuse. Let's just bump VERSION yet
another time.
@paride
Copy link
Collaborator Author

paride commented Feb 20, 2024

I think this happened because I pushed the previous PR to the main branch of my fork. My fork does not have the pypi creds, but when I opened the PR I allowed creds sharing with the fork, which were needed to actually test my changes to the main-check job. However this also created the tag and pushed to pypi, pre-merge.

Once the merge happened, the real main-check jobs tried to do the same, and failed. I tried to clear the release, but that is not enough, as explained in the commit message. So here we are.

@paride paride changed the title No-change bump VERSION to 6.0.3 No-change VERSION bump to 6.0.3 Feb 20, 2024
@paride paride merged commit f21f534 into canonical:main Feb 20, 2024
4 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.

2 participants