Skip to content

Fix issue with publishing release#222

Merged
sethmlarson merged 2 commits intopython-hyper:mainfrom
ngoldbaum:fix-release
Mar 5, 2026
Merged

Fix issue with publishing release#222
sethmlarson merged 2 commits intopython-hyper:mainfrom
ngoldbaum:fix-release

Conversation

@ngoldbaum
Copy link
Contributor

@ngoldbaum ngoldbaum commented Mar 4, 2026

c.f. #221 (comment)

I'm not 100% sure this will work. Unfortunately the only way to test it (I think?) is to merge this and push a new tag.

@sethmlarson should I push a v1.2.1.1 tag, or is it OK to simply move the v1.2.1.0 tag to a version after this PR is merged, since the PyPI upload never happened?

Copy link

@hugovk hugovk left a comment

Choose a reason for hiding this comment

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

@ngoldbaum
Copy link
Contributor Author

@hugovk showed up because I linked here on the PyPA discord. He also suggested migrating to trusted publishing, but I think that will need some help from @sethmlarson to adjust the PyPI settings.

@sethmlarson
Copy link
Member

@ngoldbaum I think we should configure trusted publishers. Let me do that quickly and then we can drop all the API token configurations.

@sethmlarson
Copy link
Member

@ngoldbaum Also, what is your PyPI username? I am going to invite you as a collaborator there, too.

@sethmlarson
Copy link
Member

@ngoldbaum You can delete the old tag since it was never published and re-push a new one.

@ngoldbaum
Copy link
Contributor Author

My PyPI username is Nathan.Goldbaum: https://pypi.org/user/Nathan.Goldbaum/

Looks like everything is OK here. I'll delete the tag now and push a new one once this is merged.

@sethmlarson sethmlarson merged commit 69f2b7f into python-hyper:main Mar 5, 2026
30 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