Skip to content

feat(stoneintg-1350): add support for nested componentGroups #8845

feat(stoneintg-1350): add support for nested componentGroups

feat(stoneintg-1350): add support for nested componentGroups #8845

Triggered via pull request June 15, 2026 18:37
Status Success
Total duration 6m 1s
Artifacts

pr.yaml

on: pull_request
Check Dockerfiles
19s
Check Dockerfiles
Go linters
5m 57s
Go linters
Check sources
5m 2s
Check sources
Run gitlint checks
14s
Run gitlint checks
kube-linter
8s
kube-linter
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 10 warnings
Check sources
Cannot open: File exists
Check sources
Cannot open: File exists
Check sources
Cannot open: File exists
Check sources
Cannot open: File exists
Check sources
Cannot open: File exists
Check sources
Cannot open: File exists
Check sources
Cannot open: File exists
Check sources
Cannot open: File exists
Check sources
Cannot open: File exists
Check sources
Cannot open: File exists
kube-linter
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 16th, 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/
Run gitlint checks
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 16th, 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/
Check Dockerfiles
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 16th, 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/
Check sources
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Check sources
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
Check sources
Restore cache failed: Dependencies file is not found in /home/runner/work/integration-service/integration-service. Supported file pattern: go.sum
Go linters
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-go@v5, golangci/golangci-lint-action@v8. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Go linters
Unexpected input(s) 'skip-cache', valid inputs are ['version', 'min-go-version', 'build-tags', 'checks', 'install-go', 'use-cache', 'cache-key', 'working-directory', 'output-format', 'output-file', 'merge-files']
Go linters
Unexpected input(s) 'skip-cache', valid inputs are ['version', 'min-go-version', 'build-tags', 'checks', 'install-go', 'use-cache', 'cache-key', 'working-directory', 'output-format', 'output-file', 'merge-files']
Go linters
Restore cache failed: Dependencies file is not found in /home/runner/work/integration-service/integration-service. Supported file pattern: go.sum