CI: Use trusted publishing with release workflow
- Dominant language
- Python
- Stars
- 10
- Forks
- 5
- Avg merge
- 7d 5h
- Merged PRs (30d)
- 7
Description
## About
The automatic release workflow works well, but the report shows it can be improved.
```
Warning: The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
Warning: Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Warning: A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
```
-- https://github.com/crate/cratedb-toolkit/actions/runs/21890606665
-- https://github.com/crate/cratedb-toolkit/actions/runs/21890606665/job/63195397630#step:6:168
## References
- https://github.com/crate/crash/issues/486
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.