gh-action-pypi-publish
zig-releaser
Our great sponsors
| gh-action-pypi-publish | zig-releaser | |
|---|---|---|
| 5 | 1 | |
| 836 | 10 | |
| 3.7% | - | |
| 8.1 | 2.6 | |
| 1 day ago | 6 months ago | |
| Python | Shell | |
| BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gh-action-pypi-publish
-
PyPI new user and new project registrations temporarily suspended
> Recently I've seen someone on Reddit trying to automate the creation of PyPI projects through GitHub Actions. The person was complaining that the first deployment couldn't use an API key for that project since it didn't exist. So I'm not surprised some people are trying to do the same for malicious purposes.
Sorry for the tangent, but: you can do this now! If you use trusted publishing, you can register a "pending publisher" for a project that doesn't exist yet. When the trusted publisher (like GitHub Actions) is used, it'll create the project[1].
All of this is supported transparently by the official publishing action for GitHub Actions[2].
[1]: https://docs.pypi.org/trusted-publishers/creating-a-project-...
[2]: https://github.com/pypa/gh-action-pypi-publish
-
Publishing to PyPI via GitHub Action
In the documentation example, I see that the action yaml file contains the line uses: pypa/gh-action-pypi-publish@release/v1. I have never done this before and almost went with that, but I am not sure why the example shows v1 hardcoded, so I don't think I actually want this to happen. It doesn't seem to be well explained though, and the pypi-publish action repo was also quiet on this. Is this saying that it will create a release branch in my repo and call the release v1? Or how will this appear after I've done it? Will I have to manually change this v1 to v0.1.1 in the actions file AND the pyproject.toml?
-
"Even with --dry-run pip will execute arbitrary code found in the package's setup.py. In fact, merely asking pip to download a package can execute arbitrary code"
Yeah, you're uploading to PyPi in your pipeline, great. The custom github action still uses twine because the stdlib falls short on BASIC security. https://github.com/pypa/gh-action-pypi-publish/blob/unstable/v1/twine-upload.sh
-
Do you publish pypi source code to Github as well in the same form?
I never bothered with pypi myself but I hope the nudge into github actions helps you. I've found the following promising github action: https://github.com/pypa/gh-action-pypi-publish
- The Python Package Index is now a GitHub secret scanning integrator
zig-releaser
What are some alternatives?
build - A simple, correct Python build frontend
release - Contains every things needed to release jenkins core from the jenkins infra project
git-filter-repo - Quickly rewrite git repository history (filter-branch replacement)
rolling-rhino - Rolling Rhino; convert Ubuntu into a rolling release. As seen on YouTube 📺
amplify-preview-actions - This action deploys your AWS Amplify pull request preview for your public repository
go-release-action - Automatically publish Go binaries to Github Release Assets through Github Action.
git-repo-sync - Git Repo Sync enables you to synchronize code to other code management platforms, such as GitLab, Gitee, etc.
release-manager - 🎁 Ragdata's Automated Release & Deployment Bot with CHANGELOG
trufflehog - Find and verify credentials
semantic-release - :package::rocket: Fully automated version management and package publishing
roadmap - GitHub public roadmap