Skip to content

Promote Main to Release Branches #61

Promote Main to Release Branches

Promote Main to Release Branches #61

Manually triggered March 11, 2026 14:14
Status Success
Total duration 43s
Artifacts

release.yml

on: workflow_dispatch
Generate HeadVer Tag  /  generate_tag
10s
Generate HeadVer Tag / generate_tag
Create GitHub Release
9s
Create GitHub Release
Promote main -> release branch(es)
11s
Promote main -> release branch(es)
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Generate HeadVer Tag / generate_tag
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. 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/
Generate HeadVer Tag / generate_tag
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Create GitHub Release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, ncipollo/release-action@v1. 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/
Create GitHub Release
Unexpected input(s) 'release_name', valid inputs are ['allowUpdates', 'artifactErrorsFailBuild', 'artifact', 'artifacts', 'artifactContentType', 'body', 'bodyFile', 'commit', 'discussionCategory', 'draft', 'generateReleaseNotes', 'generateReleaseNotesPreviousTag', 'immutableCreate', 'makeLatest', 'name', 'omitBody', 'omitBodyDuringUpdate', 'omitDraftDuringUpdate', 'omitName', 'omitNameDuringUpdate', 'omitPrereleaseDuringUpdate', 'owner', 'prerelease', 'removeArtifacts', 'replacesArtifacts', 'repo', 'skipIfReleaseExists', 'tag', 'token', 'updateOnlyUnreleased']
Promote main -> release branch(es)
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/