Automate PyPi version updates
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
Research direction
Start by reading the existing workflows under .github/workflows, especially any release/tag workflow and the CI setup that already stores SNOPT secrets. Compare that with the linked GitHub Actions/PyPI publishing example, then add a workflow triggered by a tagged release that builds and publishes the package using a stored PyPI token. Done means a tag can publish automatically without manual admin updates, ideally verified with a test release or dry run.
Written by the indexing model from the issue text.
Description
Desired capability or behavior.
When a tagged release is created on github, it would be helpful for PyPi to automatically get sent that release, rather than relying on the OM group admin to manually update
Suggested implementation.
There are probably several ways to accomplish this. I found a demonstration using github actions on this website:
https://jackwhitworth.com/blog/automatically-update-pypi-on-github-release/
That may be applicable to our use case - all it would require is PyPi login info to be added to the secrets, which I believe we already use for SNOPT in CI testing?
- Dominant language
- Python
- Stars
- 294
- Forks
- 144
- Avg merge
- 12d 2h
- Merged PRs (30d)
- 6
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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.
More from OpenMDAO/Aviary
-
request
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 3 days
-
Move mass_per_flight_crew to Aviary variablePossibly taken @xjjiang claimed this 21 days ago. Openrequest
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
OpenMDAO/Aviary#1190 · 1 assignee ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 3 days
-
Simplify how mission range is specifiedPossibly taken @ehariton claimed this 2 days ago. Openrequest
OpenMDAO/Aviary#1347 · 1 comment · 4 assignees ·
Maintainers usually reply within 3 days
-
request
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 3 days
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ClockGU/clockwork-backend#169 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
aws-samples/sample-per-model-bedrock#616 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
chnm/teachinghistory-hugo#47 ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
pandas-dev/pandas-stubs#2047 · 2 comments ·
Maintainers usually reply within 1 day