CI cannot release to PyPI after project rename
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 28/100
Research direction
Start with the linked GitHub Actions run and inspect the release configuration involved in publishing to PyPI after the move to pytorch/tlparse. Confirm which project name and credentials are being used, then verify that a release can publish to PyPI alongside the existing cargo release and that pip install tlparse receives new versions.
Written by the indexing model from the issue text.
Description
Since we changed our project name from ezyang/tlparse to pytorch/tlparse, PyPi.org no longer recognizes our openconnect credentials: https://github.com/pytorch/tlparse/actions/runs/13314207315/job/37184452995
I believe just changing our config to be the correct name will fix the problem, but I haven't debugged further.
We can still release on cargo so we're unblocked internally, but this makes it so we can't release to PyPi at the same time, so pip install tlparse isn't getting new versions.
Unfortunately, I think only @ezyang (who's on leave) has permissions to update PyPI at the moment.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Getting set up
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 meta-pytorch/tlparse
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
meta-pytorch/tlparse#162 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
meta-pytorch/tlparse#161 · 5 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
meta-pytorch/tlparse#153 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
meta-pytorch/tlparse#142 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
meta-pytorch/tlparse#141 · 1 comment ·
All issues in meta-pytorch/tlparse
Similar issues
-
`categorize_command` has no `uv` arm, so every `rtk uv …` row counts as `other` in the ecosystem mixOpenarea:api bug good first issue priority:low
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
area/cli kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
good first issue open-endedness: low type: new feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100