Use correct version for gRPC publication in dev-release workflow #330
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
dev-build.yml
on: push
Collect app version
/
Pre-build steps for project .
18s
Collect grpc version
/
Pre-build steps for project grpc
16s
Build and publish Java gRPC distributions
/
Build Gradle module grpc
1m 58s
owasp-scan
/
owasp-scan-job
4m 24s
Build and publish Python distributions to PyPI
/
Build and publish Python distributions to PyPI
2m 44s
Scan Docker image for vulnerabilities
/
trivy-scan-job
40s
Annotations
1 error, 2 warnings, and 1 notice
owasp-scan / owasp-scan-job
Process completed with exit code 1.
|
Build and publish Python distributions to PyPI / Build and publish Python distributions to PyPI
The following actions uses node12 which is deprecated and will be forced to run on node16: MerthinTechnologies/edit-json-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
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
|
Build and publish Python distributions to PyPI / Build and publish Python distributions to PyPI
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
|