Skip to content

Merge pull request #26 from JacksonBurns/v1-1/jcheminf_revisions #358

Merge pull request #26 from JacksonBurns/v1-1/jcheminf_revisions

Merge pull request #26 from JacksonBurns/v1-1/jcheminf_revisions #358

Triggered via push January 16, 2025 21:43
Status Success
Total duration 14m 42s
Artifacts

CI.yml

on: push
Check Formatting Errors
1m 56s
Check Formatting Errors
Matrix: build-and-test
check-for-new-release
11s
check-for-new-release
Build and publish Python distributions to PyPI
20s
Build and publish Python distributions to PyPI
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
Check Formatting Errors
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
ubuntu-latest Python 3.11 Subtest
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
ubuntu-latest Python 3.9 Subtest
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
ubuntu-latest Python 3.10 Subtest
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
ubuntu-latest Python 3.12 Subtest
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
ubuntu-latest Python 3.8 Subtest
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
check-for-new-release
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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):