fix: correct JSON serialization and error handling in VaultHttp #81
spbsolublekeyfactor-bootstrap-workflow.yml
on: pull_request
call-starter-workflow
/
...
/
Set workflow variables from integration-manifest.json
5s
call-starter-workflow
/
...
/
Grep TODO and License Headers
7s
call-starter-workflow
/
Detect Primary Language
5s
call-starter-workflow
/
...
/
create-github-release-workflow
6s
call-starter-workflow
/
Check for .goreleaser file
3s
call-starter-workflow
/
setup_platforms
4s
call-starter-workflow
/
...
/
polaris_scan
7s
call-starter-workflow
/
...
/
Use private doctool action in public repository
call-starter-workflow
/
...
/
Configure branch protection
call-starter-workflow
/
...
/
Updating repository settings
call-starter-workflow
/
...
/
update-catalog-entry
call-starter-workflow
/
...
/
create-github-release
7s
call-starter-workflow
/
...
/
Create PR from release branch to main
call-starter-workflow
/
...
/
dotnet-build-and-release
2m 8s
call-starter-workflow
/
...
/
run-goreleaser
Annotations
2 errors and 3 warnings
|
call-starter-workflow / call-polaris-scan-workflow / polaris_scan
Workflow failed! [polaris_access_token] - required parameters for polaris is missing
|
|
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release
Process completed with exit code 1.
|
|
call-starter-workflow / call-polaris-scan-workflow / polaris_scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: blackduck-inc/black-duck-security-scan@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-create-github-release-workflow / create-github-release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/action-bump-semver@v1, keyfactor/action-create-release@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-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. 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/
|