v1.41.0.post1 #39
Triggered via release
October 24, 2023 09:47
angrybayblade
angrybayblade
published
v1.41.0.post1
Status
Success
Total duration
15m 50s
Artifacts
–
release.yml
on: release
Matrix: Create Framework & Plugin Releases
Matrix: Push Open AEA Packages
Publish Docs Images
1m 58s
Publish User Images
9m 54s
Publish Deploy Images
5m 40s
Publish Develop Images
8m 28s
Annotations
19 warnings and 9 notices
|
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
|
|
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
|
|
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/
|