Merge pull request #4074 from aboutcode-org/release-prep-v32.3.1 #76
AyanSinhaMahapatrascancode-release.yml
on: push
Matrix: Build PyPI wheels
Matrix: Build app Release for linux
Matrix: Build app Release for mac
Matrix: Build app Release for windows
Build app source
4m 34s
Build PyPI sdist archives
1m 20s
Matrix: Test PyPI wheels on linux and mac
Matrix: Test PyPI wheels on Windows
Matrix: smoke_test_install_and_run_app_archives_on_linux
Matrix: smoke_test_install_and_run_app_archives_on_macos
Matrix: smoke_test_install_and_run_app_archives_on_windows
Matrix: Publish to PyPI
Annotations
16 warnings
|
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):
|
|
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):
|
|
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):
|
|
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):
|
|
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):
|
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "linux_app_py_3.10", "linux_app_py_3.11", "linux_app_py_3.12", "linux_app_py_3.9", "macos_app_py_3.10", "macos_app_py_3.11", "macos_app_py_3.12", "macos_app_py_3.9", "sdists", "source_app", "wheels-3.10", "wheels-3.11", "wheels-3.12", "wheels-3.9", "windows_app_py_3.10", "windows_app_py_3.11", "windows_app_py_3.12", "windows_app_py_3.9".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
linux_app_py_3.10
|
202 MB |
|
|
linux_app_py_3.11
|
203 MB |
|
|
linux_app_py_3.12
|
203 MB |
|
|
linux_app_py_3.9
|
202 MB |
|
|
macos_app_py_3.10
|
154 MB |
|
|
macos_app_py_3.11
|
154 MB |
|
|
macos_app_py_3.12
|
154 MB |
|
|
macos_app_py_3.9
|
154 MB |
|
|
sdists
|
29.3 MB |
|
|
source_app
|
129 MB |
|
|
wheels-3.10
|
219 MB |
|
|
wheels-3.11
|
219 MB |
|
|
wheels-3.12
|
219 MB |
|
|
wheels-3.9
|
219 MB |
|
|
windows_app_py_3.10
|
145 MB |
|
|
windows_app_py_3.11
|
145 MB |
|
|
windows_app_py_3.12
|
145 MB |
|
|
windows_app_py_3.9
|
145 MB |
|