Skip to content

Merge pull request #176 from octoenergy/release-6.1 #33

Merge pull request #176 from octoenergy/release-6.1

Merge pull request #176 from octoenergy/release-6.1 #33

Triggered via push October 30, 2024 09:44
Status Success
Total duration 56s
Artifacts
Build and publish Python 🐍 distributions πŸ“¦ to PyPI and TestPyPI
46s
Build and publish Python 🐍 distributions πŸ“¦ to PyPI and TestPyPI
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Build and publish Python 🐍 distributions πŸ“¦ to PyPI and TestPyPI
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
attestations input ignored
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.
Upgrade to Trusted Publishing
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
Create a Trusted Publisher
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):
attestations input ignored
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.
Upgrade to Trusted Publishing
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
Create a Trusted Publisher
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):