chore(docs): update CHANGELOG #344
keyfactor-bootstrap-workflow.yml
on: push
call-starter-workflow
/
...
/
Set workflow variables from integration-manifest.json
8s
call-starter-workflow
/
...
/
Grep TODO and License Headers
4s
call-starter-workflow
/
Detect Primary Language
21s
call-starter-workflow
/
Check for .goreleaser file
7s
call-starter-workflow
/
setup_platforms
11s
call-starter-workflow
/
...
/
create-github-release-workflow
5s
call-starter-workflow
/
...
/
Use private doctool action in public repository
1m 20s
call-starter-workflow
/
...
/
build
call-starter-workflow
/
...
/
Configure branch protection
call-starter-workflow
/
...
/
Updating repository settings
call-starter-workflow
/
...
/
update-catalog-entry
call-starter-workflow
/
...
/
create-github-release
call-starter-workflow
/
...
/
Get Release Properties
3s
call-starter-workflow
/
...
/
setup
2s
call-starter-workflow
/
...
/
Create PR from release branch to main
call-starter-workflow
/
...
/
dotnet-build-and-release
call-starter-workflow
/
...
/
Build and Possibly release maven hpi artifact
call-starter-workflow
/
...
/
run-goreleaser
Matrix: call-starter-workflow / call-container-build-and-release-workflow / Build Containers
call-starter-workflow
/
...
/
merge
12s
Annotations
24 warnings
|
Workflow syntax warning:
keyfactor/actions/.github/workflows/starter.yml@3.2.0#L125
In keyfactor/actions/.github/workflows/starter.yml@3.2.0 (Line: 125, Col: 11): Error from called workflow keyfactor/actions/.github/workflows/maven-build-and-release.yml@v3 (Line: 53, Col: 13): Conditional expression contains literal text outside replacement tokens. This will cause the expression to always evaluate to truthy. Did you mean to put the entire expression inside ${{ }}?
|
|
Workflow syntax warning:
keyfactor/actions/.github/workflows/starter.yml@3.2.0#L125
In keyfactor/actions/.github/workflows/starter.yml@3.2.0 (Line: 125, Col: 11): Error from called workflow keyfactor/actions/.github/workflows/maven-build-and-release.yml@v3 (Line: 61, Col: 13): Conditional expression contains literal text outside replacement tokens. This will cause the expression to always evaluate to truthy. Did you mean to put the entire expression inside ${{ }}?
|
|
call-starter-workflow / Check for .goreleaser file
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/checkout@v4, keyfactor/file-existence-action@v3. 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/
|
|
call-starter-workflow / call-create-github-release-workflow / create-github-release-workflow
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/checkout@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/
|
|
call-starter-workflow / call-create-github-release-workflow / call-check-file-action / Grep TODO and License Headers
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. 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/
|
|
call-starter-workflow / Detect Primary Language
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/action-get-primary-language@v2, keyfactor/checkout@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/
|
|
call-starter-workflow / setup_platforms
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/checkout@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/
|
|
call-starter-workflow / call-assign-from-json-workflow / Set workflow variables from integration-manifest.json
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./tools, keyfactor/checkout@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/
|
|
call-starter-workflow / call-generate-readme-workflow / Use private doctool action in public repository
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, Keyfactor/add-and-commit@v9.1.3, keyfactor/checkout@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/
|
|
call-starter-workflow / call-container-build-and-release-workflow / Build Containers (linux/amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/build-push-action@v6.0.1, keyfactor/checkout@v4, keyfactor/login-action@v3.2.0, keyfactor/metadata-action@v5.5.1, keyfactor/setup-buildx-action@v3.3.0, keyfactor/setup-qemu-action@v3.0.0, keyfactor/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/
|
|
call-starter-workflow / call-container-build-and-release-workflow / Build Containers (linux/amd64)
No Docker tag has been generated. Check tags input.
|
|
call-starter-workflow / call-container-build-and-release-workflow / Build Containers (linux/amd64)
No Docker image version has been generated. Check tags input.
|
|
call-starter-workflow / call-container-build-and-release-workflow / Build Containers (linux/ppc64le)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/build-push-action@v6.0.1, keyfactor/checkout@v4, keyfactor/login-action@v3.2.0, keyfactor/metadata-action@v5.5.1, keyfactor/setup-buildx-action@v3.3.0, keyfactor/setup-qemu-action@v3.0.0, keyfactor/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/
|
|
call-starter-workflow / call-container-build-and-release-workflow / Build Containers (linux/ppc64le)
No Docker tag has been generated. Check tags input.
|
|
call-starter-workflow / call-container-build-and-release-workflow / Build Containers (linux/ppc64le)
No Docker image version has been generated. Check tags input.
|
|
call-starter-workflow / call-container-build-and-release-workflow / Build Containers (linux/s390x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/build-push-action@v6.0.1, keyfactor/checkout@v4, keyfactor/login-action@v3.2.0, keyfactor/metadata-action@v5.5.1, keyfactor/setup-buildx-action@v3.3.0, keyfactor/setup-qemu-action@v3.0.0, keyfactor/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/
|
|
call-starter-workflow / call-container-build-and-release-workflow / Build Containers (linux/s390x)
No Docker tag has been generated. Check tags input.
|
|
call-starter-workflow / call-container-build-and-release-workflow / Build Containers (linux/s390x)
No Docker image version has been generated. Check tags input.
|
|
call-starter-workflow / call-container-build-and-release-workflow / Build Containers (linux/arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/build-push-action@v6.0.1, keyfactor/checkout@v4, keyfactor/login-action@v3.2.0, keyfactor/metadata-action@v5.5.1, keyfactor/setup-buildx-action@v3.3.0, keyfactor/setup-qemu-action@v3.0.0, keyfactor/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/
|
|
call-starter-workflow / call-container-build-and-release-workflow / Build Containers (linux/arm64)
No Docker tag has been generated. Check tags input.
|
|
call-starter-workflow / call-container-build-and-release-workflow / Build Containers (linux/arm64)
No Docker image version has been generated. Check tags input.
|
|
call-starter-workflow / call-container-build-and-release-workflow / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/download-artifact@v4.1.7, keyfactor/login-action@v3.2.0, keyfactor/metadata-action@v5.5.1, keyfactor/setup-buildx-action@v3.3.0. 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/
|
|
call-starter-workflow / call-container-build-and-release-workflow / merge
No Docker tag has been generated. Check tags input.
|
|
call-starter-workflow / call-container-build-and-release-workflow / merge
No Docker image version has been generated. Check tags input.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Keyfactor~command-cert-manager-issuer~0WYQLJ.dockerbuild
|
22.6 KB |
sha256:53dc5588d698dd0c0cb8f6f7caa04ee8b347dfc00df49881208fd707af084444
|
|
|
Keyfactor~command-cert-manager-issuer~9B9E9W.dockerbuild
|
22.3 KB |
sha256:a2e66ed7521d0ebb8de9e983d110417f2f9a58f17ab62a95949f7f274406571d
|
|
|
Keyfactor~command-cert-manager-issuer~L80KBD.dockerbuild
|
51.7 KB |
sha256:eed852f1aaa633e2d1a99a550159d777de80ae0f8a38f900a2c65146209376de
|
|
|
Keyfactor~command-cert-manager-issuer~WWRFQJ.dockerbuild
|
21.3 KB |
sha256:1e2d9305f99533e417e78e6c21cc52b23d37dd7f5c10289608fb88c5d3a4856a
|
|
|
digests-linux-amd64
Expired
|
244 Bytes |
sha256:d93b7b82ba403038c90c03739c9eb8c3480dc3ef502715223a920df39e79636e
|
|
|
digests-linux-arm64
Expired
|
244 Bytes |
sha256:08102ea3012dab5b7e225b56fdc576e5a7b349bfe999af4bd04d74a03be5532a
|
|
|
digests-linux-ppc64le
Expired
|
244 Bytes |
sha256:71981e819f11376dc30f069fde7971ccafe7079822bea4735e4cf7628c8891d9
|
|
|
digests-linux-s390x
Expired
|
244 Bytes |
sha256:8eb74ea904ec697ad4316a2f5ff9ab32a341de764e454203744d775d6f5d54b6
|
|
|
licenselogs
|
146 Bytes |
sha256:194a5b809e7afc933b658c18a664c38f3ba368511efb6ce229c860c6e908cc86
|
|
|
todologs
|
140 Bytes |
sha256:c1bc54e00ec0c2ebca6b96c2786934eb0c87f57ed7502d10626ac3af0618d713
|
|