🚀 Release Trigger #14
release_trigger.yml
on: workflow_dispatch
call-release-trigger
/
...
/
verify-release
4s
call-release-trigger
/
...
/
verify_secrets
3s
call-release-trigger
/
...
/
verify_variables
4s
call-release-trigger
/
...
/
validate-pr-information
6s
call-release-trigger
/
...
/
build-from-branch
31s
call-release-trigger
/
...
/
update-branch
37s
call-release-trigger
/
...
/
verify-created-release
3s
Annotations
4 warnings and 3 notices
|
call-release-trigger / merge-to-main / merge-to-main
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/
|
|
call-release-trigger / build-from-main / build-from-branch
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. 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-release-trigger / create-release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@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/
|
|
call-release-trigger / update-develop / update-branch
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/
|
|
call-release-trigger / verify-repo-secrets / verify_secrets
All required secrets are present.
|
|
call-release-trigger / verify-repo-vars / verify_variables
All required variables are present.
|
|
call-release-trigger / verify-release / verify-created-release
Success, release found with the expected name 1.3.4.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
flame-package
Expired
|
96.1 KB |
sha256:18d64a511c9e796e2a43728a10dbb4cb3f545913a548db7017d4d94ae2562cb2
|
|