Automate release process
Open
Nobody has claimed this yet.
feature
infrastructure
P2
- Dominant language
- Python
- Stars
- 18.8k
- Forks
- 2.8k
- Avg merge
- 16h 26m
- Merged PRs (30d)
- 21
Description
- We could release to test pypi every time the
mainbranch is updated - We could have a github action that releases to pypi. It could be triggered from the "Actions" tab in github
- A couple examples of good releases:
- Dash Ag Grid: https://github.com/plotly/dash-ag-grid/
- Databricks OAuth: https://github.com/plotly/dash-dbx-connect
- Ensure support for Digital Attestations: https://blog.pypi.org/posts/2024-11-14-pypi-now-supports-digital-attestations/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files or tests are named. Start by reviewing the GitHub Actions entry point for updates to main and the current PyPI packaging and release setup, then compare the Dash Ag Grid and Databricks OAuth examples. Done means test-PyPI releases on main updates, manually triggerable PyPI releases, and Digital Attestations support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100