Release Flow #33
Triggered via release
August 11, 2023 08:57
angrybayblade
angrybayblade
published
a98a707
Status
Failure
Total duration
20m 38s
Artifacts
–
release.yml
on: release
Matrix: Create Framework & Plugin Releases
Matrix: Push Open AEA Packages
Publish Docs Images
10s
Publish User Images
7m 49s
Publish Deploy Images
6m 16s
Publish Develop Images
6m 7s
Annotations
1 error, 19 warnings, and 9 notices
|
Publish Docs Images
Process completed with exit code 125.
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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 Framework & Plugin Releases (ubuntu-latest, 3.10)
The process '/usr/bin/git' failed with exit code 128
|
|
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
|
|
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
|
|
Push Open AEA Packages (ubuntu-latest, 3.10)
The process '/usr/bin/git' failed with exit code 128
|
|
Publish Docs Images
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Publish Docs Images
The process '/usr/bin/git' failed with exit code 128
|
|
Publish Deploy Images
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Publish Deploy Images
The process '/usr/bin/git' failed with exit code 128
|
|
Publish Develop Images
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Publish Develop Images
The process '/usr/bin/git' failed with exit code 128
|
|
Publish User Images
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Publish User Images
The process '/usr/bin/git' failed with exit code 128
|
|
Create Framework & Plugin Releases (ubuntu-latest, 3.10)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
|
Create Framework & Plugin Releases (ubuntu-latest, 3.10)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
|
Create Framework & Plugin Releases (ubuntu-latest, 3.10)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
|
Create Framework & Plugin Releases (ubuntu-latest, 3.10)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
|
Create Framework & Plugin Releases (ubuntu-latest, 3.10)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
|
Create Framework & Plugin Releases (ubuntu-latest, 3.10)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
|
Create Framework & Plugin Releases (ubuntu-latest, 3.10)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
|
Create Framework & Plugin Releases (ubuntu-latest, 3.10)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|
|
Create Framework & Plugin Releases (ubuntu-latest, 3.10)
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|