Add .NET 10 target framework support #63
keyfactor-starter-workflow.yml
on: push
call-starter-workflow
/
...
/
Set workflow variables from integration-manifest.json
8s
call-starter-workflow
/
...
/
Grep TODO and License Headers
7s
call-starter-workflow
/
Detect Primary Language
7s
call-starter-workflow
/
Check for .goreleaser file
6s
call-starter-workflow
/
setup_platforms
7s
call-starter-workflow
/
...
/
create-github-release-workflow
5s
call-starter-workflow
/
...
/
Use private doctool action in public repository
1m 37s
call-starter-workflow
/
...
/
Configure branch protection
call-starter-workflow
/
...
/
Updating repository settings
call-starter-workflow
/
...
/
update-catalog-entry
call-starter-workflow
/
...
/
create-github-release
0s
call-starter-workflow
/
...
/
Get Release Properties
call-starter-workflow
/
...
/
setup
call-starter-workflow
/
...
/
Create PR from release branch to main
call-starter-workflow
/
...
/
dotnet-build-and-release
1m 29s
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
Waiting for pending jobs
call-starter-workflow
/
...
/
merge
Annotations
23 warnings
|
Workflow syntax warning:
keyfactor/actions/.github/workflows/starter.yml@v3#L125
In keyfactor/actions/.github/workflows/starter.yml@v3 (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@v3#L125
In keyfactor/actions/.github/workflows/starter.yml@v3 (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 / 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 / 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 / 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 / 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 / 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 / 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, keyfactor/setup-dotnet@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:
HydrantCAProxy/HydrantIdCAPlugin.cs#L557
'X509Certificate2.X509Certificate2(byte[])' is obsolete: 'Loading certificate data through the constructor or Import is obsolete. Use X509CertificateLoader instead to load certificates.' (https://aka.ms/dotnet-warnings/SYSLIB0057)
|
|
call-starter-workflow / call-generate-readme-workflow / Use private doctool action in public repository:
HydrantCAProxy/HydrantIdCAPlugin.cs#L388
'X509Certificate2Collection.Import(byte[])' is obsolete: 'Loading certificate data through the constructor or Import is obsolete. Use X509CertificateLoader instead to load certificates.' (https://aka.ms/dotnet-warnings/SYSLIB0057)
|
|
call-starter-workflow / call-generate-readme-workflow / Use private doctool action in public repository:
HydrantCAProxy/Client/Authentication/Hawk.cs#L569
'HashAlgorithm.Create(string)' is obsolete: 'Cryptographic factory methods accepting an algorithm name are obsolete. Use the parameterless Create factory method on the algorithm type instead.' (https://aka.ms/dotnet-warnings/SYSLIB0045)
|
|
call-starter-workflow / call-generate-readme-workflow / Use private doctool action in public repository:
HydrantCAProxy/Client/Authentication/Hawk.cs#L569
'HashAlgorithm.Create(string)' is obsolete: 'Cryptographic factory methods accepting an algorithm name are obsolete. Use the parameterless Create factory method on the algorithm type instead.' (https://aka.ms/dotnet-warnings/SYSLIB0045)
|
|
call-starter-workflow / call-generate-readme-workflow / Use private doctool action in public repository:
HydrantCAProxy/HydrantIdCAPlugin.cs#L557
'X509Certificate2.X509Certificate2(byte[])' is obsolete: 'Loading certificate data through the constructor or Import is obsolete. Use X509CertificateLoader instead to load certificates.' (https://aka.ms/dotnet-warnings/SYSLIB0057)
|
|
call-starter-workflow / call-generate-readme-workflow / Use private doctool action in public repository:
HydrantCAProxy/HydrantIdCAPlugin.cs#L388
'X509Certificate2Collection.Import(byte[])' is obsolete: 'Loading certificate data through the constructor or Import is obsolete. Use X509CertificateLoader instead to load certificates.' (https://aka.ms/dotnet-warnings/SYSLIB0057)
|
|
call-starter-workflow / call-generate-readme-workflow / Use private doctool action in public repository:
HydrantCAProxy/Client/Authentication/Hawk.cs#L569
'HashAlgorithm.Create(string)' is obsolete: 'Cryptographic factory methods accepting an algorithm name are obsolete. Use the parameterless Create factory method on the algorithm type instead.' (https://aka.ms/dotnet-warnings/SYSLIB0045)
|
|
call-starter-workflow / call-generate-readme-workflow / Use private doctool action in public repository:
HydrantCAProxy/Client/Authentication/Hawk.cs#L569
'HashAlgorithm.Create(string)' is obsolete: 'Cryptographic factory methods accepting an algorithm name are obsolete. Use the parameterless Create factory method on the algorithm type instead.' (https://aka.ms/dotnet-warnings/SYSLIB0045)
|
|
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release
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/setup-dotnet@v4, keyfactor/setup-msbuild@v2. 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-dotnet-build-and-release-workflow / dotnet-build-and-release:
HydrantCAProxy/HydrantIdCAPlugin.cs#L557
'X509Certificate2.X509Certificate2(byte[])' is obsolete: 'Loading certificate data through the constructor or Import is obsolete. Use X509CertificateLoader instead to load certificates.' (https://aka.ms/dotnet-warnings/SYSLIB0057)
|
|
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release:
HydrantCAProxy/Client/Authentication/Hawk.cs#L569
'HashAlgorithm.Create(string)' is obsolete: 'Cryptographic factory methods accepting an algorithm name are obsolete. Use the parameterless Create factory method on the algorithm type instead.' (https://aka.ms/dotnet-warnings/SYSLIB0045)
|
|
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release:
HydrantCAProxy/HydrantIdCAPlugin.cs#L388
'X509Certificate2Collection.Import(byte[])' is obsolete: 'Loading certificate data through the constructor or Import is obsolete. Use X509CertificateLoader instead to load certificates.' (https://aka.ms/dotnet-warnings/SYSLIB0057)
|
|
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release
Targeting .NET 10.0 or higher in Visual Studio 2022 17.14 is not supported.
|
|
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release:
HydrantCAProxy/Client/Authentication/Hawk.cs#L569
'HashAlgorithm.Create(string)' is obsolete: 'Cryptographic factory methods accepting an algorithm name are obsolete. Use the parameterless Create factory method on the algorithm type instead.' (https://aka.ms/dotnet-warnings/SYSLIB0045)
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
licenselogs
|
146 Bytes |
sha256:b2c8c320124d8336eafe3247d4d0a8cb5995b33bc40ac5a3a67d8f421687b8d5
|
|
|
todologs
|
140 Bytes |
sha256:63fefb97a4c5d33e98571dbf01ed9b638af9a5ee16030e7f6a4a49136eaae18b
|
|