Skip to content

0.2.14

0.2.14 #114

Triggered via release March 25, 2026 11:42
@41tair41tair
published 0.2.14
Status Success
Total duration 3m 41s
Artifacts

build-universal.yml

on: release
build-amd64  /  Build AMD64
1m 59s
build-amd64 / Build AMD64
build-arm64  /  Build ARM64
3m 11s
build-arm64 / Build ARM64
build-universal
21s
build-universal
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
build-amd64 / Build AMD64
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-go@v4, aws-actions/configure-aws-credentials@v4, docker/login-action@v2, docker/metadata-action@v5. 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/
build-amd64 / Build AMD64
Unexpected input(s) 'registry', valid inputs are ['http-proxy', 'mask-password', 'registries', 'registry-type', 'skip-logout']
build-amd64 / Build AMD64
Unexpected input(s) 'registry', valid inputs are ['http-proxy', 'mask-password', 'registries', 'registry-type', 'skip-logout']
build-arm64 / Build ARM64
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-go@v4, aws-actions/configure-aws-credentials@v4, docker/login-action@v2, docker/metadata-action@v5. 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/
build-arm64 / Build ARM64
Unexpected input(s) 'registry', valid inputs are ['http-proxy', 'mask-password', 'registries', 'registry-type', 'skip-logout']
build-arm64 / Build ARM64
Unexpected input(s) 'registry', valid inputs are ['http-proxy', 'mask-password', 'registries', 'registry-type', 'skip-logout']
build-universal
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/configure-aws-credentials@v4, docker/login-action@v2, docker/metadata-action@v5. 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/
build-universal
Unexpected input(s) 'registry', valid inputs are ['http-proxy', 'mask-password', 'registries', 'registry-type', 'skip-logout']
build-universal
Unexpected input(s) 'registry', valid inputs are ['http-proxy', 'mask-password', 'registries', 'registry-type', 'skip-logout']