Update upstream versions #2997
master_release.yml
on: push
Matrix: run_ci / cmis_tas_tests_elasticsearch
Matrix: run_ci / distribution_zip_content_tests
Matrix: run_ci / single_pipeline_image_tests
Matrix: run_ci / tas_test_with_mtls
Matrix: run_ci / tas_tests
Matrix: run_ci / tas_tests_search_api
Matrix: run_ci / tas_tests_with_aims
Matrix: run_ci / upgrade_tas_tests
run_ci
/
Pre-Commit checks
5m 11s
run_ci
/
Source Clear Scan (SCA)
4m 57s
run_ci
/
Pipeline SAST Scan - ACS
16m 6s
run_ci
/
PMD Scan
run_ci
/
CMIS TAS tests - Open Search (CMIS API)
18m 46s
run_ci
/
All AMPs tests
17m 22s
run_ci
/
Test Tomcat deployment
16m 23s
run_ci
/
Upload docker images needed for pipeline tests: <acs.version>-<PIPELINE_TAG_TEXT_INSERT>-<build>
Update latest and Single Pipeline <acs>-<build> images
0s
Update acs-community-packaging (after release)
0s
Annotations
5 warnings
|
run_ci / Transform Service Mutal TLS TAS tests with mutal TLS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
run_ci / Distribution Zip content tests (Java 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
run_ci / Pipeline SAST Scan - ACS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, veracode/Veracode-pipeline-scan-action@v1.0.16. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
run_ci / Single Pipeline image tests (Java 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
run_ci / REST API TAS tests with AIMS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Veracode Pipeline-Scan Results
Expired
|
1022 Bytes |
sha256:56f89d4afede8f199621ced95bc8eb88048a1dcd516afe2f9b9c233e70c18f02
|
|
|
Veracode Pipeline-Scan Results - ACS (Human Readable)
Expired
|
692 Bytes |
sha256:155b3b7554b2596ef516d9ddd61db4e63cec5b4529a09643dec4a45c242af8aa
|
|