Skip to content

Merge pull request #89 from maykinmedia/release/v0.19.2 #385

Merge pull request #89 from maykinmedia/release/v0.19.2

Merge pull request #89 from maykinmedia/release/v0.19.2 #385

Triggered via push January 9, 2025 18:03
Status Success
Total duration 2m 36s
Artifacts

ci.yml

on: push
Matrix: tests
Publish package to PyPI
24s
Publish package to PyPI
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
Run the test suite (Python 3.11, Django 4.2, OIDC: no)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Run the test suite (Python 3.10, Django 4.2, OIDC: no)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Run the test suite (Python 3.12, Django 4.2, OIDC: no)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Run the test suite (Python 3.10, Django 4.2, OIDC: yes)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Run the test suite (Python 3.11, Django 4.2, OIDC: yes)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Run the test suite (Python 3.12, Django 4.2, OIDC: yes)
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):