meilisearch / meilisearch/meilisearch-python
Publish to PyPI using OIDC trusted publishing
Open
Nobody has claimed this yet.
maintenance
security
- Dominant language
- Python
- Stars
- 602
- Forks
- 118
- Avg merge
- 4h 44m
- Merged PRs (30d)
- 1
Description
The workflow uploads with TWINE_USERNAME: __token__ and TWINE_PASSWORD: "pypi-${{ secrets.PYPI_API_TOKEN }}", which requires a long-lived secret; using PyPI Trusted Publishing (OIDC) would avoid secret injection and reduce exposure/rotation burden.
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
Start by locating the GitHub Actions workflow that uploads the package and inspect its current TWINE_USERNAME and TWINE_PASSWORD configuration. Update the publishing setup to use PyPI Trusted Publishing through OIDC, then verify the workflow can publish without the PYPI_API_TOKEN secret and that the long-lived token injection is removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, release, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100