Merge pull request #55 from MiraGeoscience/DEVOPS-977-zizmor-patch #16
python_deploy_dev.yml
on: push
Publish development conda package on JFrog Artifactory
/
Build package with rattler
54s
Publish development conda package on JFrog Artifactory
/
...
/
Check if version is publishable
5s
Publish development pypi package (JFrog Artifactory, TestPyPI)
/
...
/
Build poetry package
29s
Publish development pypi package (JFrog Artifactory, TestPyPI)
/
...
/
Check if version is publishable
6s
Publish development pypi package (JFrog Artifactory, TestPyPI)
/
...
/
Build setuptools package
Matrix: Publish development conda package on JFrog Artifactory / Publish package
Matrix: Publish development pypi package (JFrog Artifactory, TestPyPI) / Publish package
Publish development conda package on JFrog Artifactory
/
Add release asset
6s
Publish development pypi package (JFrog Artifactory, TestPyPI)
/
Add release asset
0s
Annotations
17 warnings
|
Publish development pypi package (JFrog Artifactory, TestPyPI) / Build poetry package / Build poetry package
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog/setup-jfrog-cli@v4.9.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Publish development pypi package (JFrog Artifactory, TestPyPI) / Publish package (public-pypi-dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog/setup-jfrog-cli@v4.4.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Publish development pypi package (JFrog Artifactory, TestPyPI) / Publish package (public-pypi-dev)
Failed while attempting to publish the build info to JFrog Artifactory: Error: The process '/opt/hostedtoolcache/jf/2.67.0/x64/jf' failed with exit code 1
|
|
Publish development pypi package (JFrog Artifactory, TestPyPI) / Publish package (public-pypi-dev)
Failed while attempting to collect Git information: Error: The process '/opt/hostedtoolcache/jf/2.67.0/x64/jf' failed with exit code 1
|
|
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):
|
|
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
|
|
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.
|
|
Publish development conda package on JFrog Artifactory / Build package with rattler
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Publish development conda package on JFrog Artifactory / Build package with rattler
No files were found with the provided path: output/**/*.tar.bz2
output/**/*.conda. No artifacts will be uploaded.
|
|
Publish development conda package on JFrog Artifactory / Build package with rattler
License file from source directory was overwritten by license file from recipe folder (/tmp/grid-appsudqGPn/info/licenses/docs/source/THIRD_PARTY_SOFTWARE.rst)
|
|
Publish development conda package on JFrog Artifactory / Build package with rattler
License file from source directory was overwritten by license file from recipe folder (/tmp/grid-appsudqGPn/info/licenses/LICENSE)
|
|
|
|
Publish development conda package on JFrog Artifactory / Build package with rattler
File already exists! Overwriting file: "/tmp/grid-appsudqGPn/info/licenses/docs/source/THIRD_PARTY_SOFTWARE.rst"
|
|
Publish development conda package on JFrog Artifactory / Build package with rattler
File already exists! Overwriting file: "/tmp/grid-appsudqGPn/info/licenses/LICENSE"
|
|
Publish development conda package on JFrog Artifactory / Publish package (public-noremote-conda-dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog/setup-jfrog-cli@v4.4.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Publish development conda package on JFrog Artifactory / Publish package (public-noremote-conda-dev)
Failed while attempting to publish the build info to JFrog Artifactory: Error: The process '/opt/hostedtoolcache/jf/2.67.0/x64/jf' failed with exit code 1
|
|
Publish development conda package on JFrog Artifactory / Publish package (public-noremote-conda-dev)
Failed while attempting to collect Git information: Error: The process '/opt/hostedtoolcache/jf/2.67.0/x64/jf' failed with exit code 1
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
grid-apps-conda-package-build
Expired
|
4.03 MB |
sha256:4441dc2fad4760d7b7e6835deee59e11c8fb5ab6553fad14ef13eb18691760ed
|
|
|
grid-apps-pip-package-build
|
45.6 KB |
sha256:838da65a44d999d28eb96faa1915e6b54e5294c6dad73827aa8c79fe9f665de0
|
|