Skip to content

Commit

Permalink
Add signing key
Browse files Browse the repository at this point in the history
  • Loading branch information
@Dreamsorcerer
Dreamsorcerer committed Mar 4, 2024
1 parent 3fbafa7 commit 0301e9c
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions README.rst
View file
Original file line number Diff line number Diff line change
Expand Up @@ -317,6 +317,8 @@ will be signed using one of the following GPG Keys:
+-------------------------+----------------+----------------------------------+
| ``E309 FD82 73BD 8465`` | Wayne Werner | waynejwerner at gmail period com |
+-------------------------+----------------+----------------------------------+
| ``5FE9 28CD 9626 CE2B`` | Sam Bull | sam at sambull period org |
+-------------------------+----------------+----------------------------------+



Expand Down

3 comments on commit 0301e9c

@webknjaz
Copy link
Member

Choose a reason for hiding this comment

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

@Dreamsorcerer FYI you can't publish GPG signatures to the PyPI anymore. It's been deprecated.

@Dreamsorcerer
Copy link
Member Author

Choose a reason for hiding this comment

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

I wasn't sure it had anything to do with PyPI originally, I just uploaded the signatures to the Github release.

@webknjaz
Copy link
Member

Choose a reason for hiding this comment

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

According to the text in the readme, the previous uploaders did publish signatures to both GH Releases and PyPI back when it was still possible. Not anymore, though. For now, I'd recommend doing sigstore signing as shown in the current version of my PyPUG guide.

Please sign in to comment.