Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
Top 8 Python release-automation Projects
-
commitizen
Create committing rules for projects :rocket: auto bump versions :arrow_up: and auto changelog generation :open_file_folder:
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
gh-action-pypi-publish
The blessed :octocat: GitHub Action, for publishing your :package: distribution files to PyPI: https://github.com/marketplace/actions/pypi-publish
-
slap
Slap is a CLI to assist in the process for developing and releasing Python packages. (by NiklasRosenstein)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
- pyscaffold
Project mention: PyPI new user and new project registrations temporarily suspended | news.ycombinator.com | 2023-05-20> 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
I don't really like writing the change log automatically from commits. I think those both have a slightly different audience and thus need different wording.
I know the frustration of merge conflicts on the change log file.
Right now, I'm creating change logs by hand which is time consuming to do on release time. I'm considering switching to using towncrier or something similar, where you have a changes dir with one file per change for creating change logs --> https://towncrier.readthedocs.io/
Project mention: Show HN: Manage SBOM vulnerabilities analysis like source code | news.ycombinator.com | 2023-06-08
Check it out on Github: https://github.com/CangyuanLi/pyproject and PyPI: https://pypi.org/project/pyproject-generator/
Python release-automation related posts
-
towncrier VS cf_changelog - a user suggested alternative
2 projects | 10 Jan 2024
- Which scaffolding package should I use?
- Show HN: Manage SBOM vulnerabilities analysis like source code
- Comment structurer mon projet Python ?
- ScheduledThreadPoolExecutor in Python
- Resources to learn how to make production quality code for projects? (using github, project organization, unit testing...)
- Show HN: Nextrelease – GitHub Action to publish the next release by merging a PR
-
A note from our sponsor - InfluxDB
www.influxdata.com | 26 Apr 2024
Index
What are some of the best open-source release-automation projects in Python? This list will help you:
Project | Stars | |
---|---|---|
1 | commitizen | 2,135 |
2 | pyscaffold | 2,009 |
3 | gh-action-pypi-publish | 836 |
4 | towncrier | 732 |
5 | slap | 18 |
6 | bogrod | 8 |
7 | nextrelease | 2 |
8 | pyproject | 2 |
Sponsored