Remove environment and permission #592
mostafaAnnotations
10 errors and 2 warnings
|
Test and build django-saml2-auth (5.0.9, 3.12, 1.8.3)
The job was canceled because "_4_2_16_3_11_1_8_3" failed.
|
|
Test and build django-saml2-auth (5.0.9, 3.12, 1.8.3)
The operation was canceled.
|
|
Test and build django-saml2-auth (4.2.16, 3.10, 1.8.3)
The job was canceled because "_4_2_16_3_11_1_8_3" failed.
|
|
Test and build django-saml2-auth (4.2.16, 3.10, 1.8.3)
The operation was canceled.
|
|
Test and build django-saml2-auth (4.2.16, 3.12, 1.8.3)
The job was canceled because "_4_2_16_3_11_1_8_3" failed.
|
|
Test and build django-saml2-auth (4.2.16, 3.12, 1.8.3)
The operation was canceled.
|
|
Test and build django-saml2-auth (5.0.9, 3.11, 1.8.3)
The job was canceled because "_4_2_16_3_11_1_8_3" failed.
|
|
Test and build django-saml2-auth (5.0.9, 3.11, 1.8.3)
The operation was canceled.
|
|
Test and build django-saml2-auth (5.0.9, 3.10, 1.8.3)
The job was canceled because "_4_2_16_3_11_1_8_3" failed.
|
|
Test and build django-saml2-auth (5.0.9, 3.10, 1.8.3)
The operation was canceled.
|
|
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):
|