Skip to content

chore: update CI workflows via baton-admin #10

chore: update CI workflows via baton-admin

chore: update CI workflows via baton-admin #10

Triggered via push March 20, 2026 22:51
Status Success
Total duration 5m 57s
Artifacts

release.yaml

on: push
release  /  validate-inputs
4s
release / validate-inputs
release  /  determine-workflows-ref
10s
release / determine-workflows-ref
release  /  goreleaser-binaries
4m 0s
release / goreleaser-binaries
release  /  goreleaser-docker
3m 13s
release / goreleaser-docker
release  /  goreleaser-windows
3m 29s
release / goreleaser-windows
release  /  record-lambda-registry
42s
release / record-lambda-registry
release  /  record-connector-registry
53s
release / record-connector-registry
release  /  record-registry-api
38s
release / record-registry-api
release  /  verify-release
28s
release / verify-release
release  /  notify-release-failure
0s
release / notify-release-failure
Fit to window
Zoom out
Zoom in

Annotations

17 warnings
release / goreleaser-docker
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v5, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3, goreleaser/goreleaser-action@v6. 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/
release / goreleaser-docker
Restore cache failed: Dependencies file is not found in /home/runner/work/baton-jamf/baton-jamf. Supported file pattern: go.mod
release / goreleaser-docker
Restore cache failed: Dependencies file is not found in /home/runner/work/baton-jamf/baton-jamf. Supported file pattern: go.mod
release / goreleaser-windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v5, goreleaser/goreleaser-action@v6. 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/
release / goreleaser-windows
Restore cache failed: Dependencies file is not found in D:\a\baton-jamf\baton-jamf. Supported file pattern: go.mod
release / goreleaser-windows
Restore cache failed: Dependencies file is not found in D:\a\baton-jamf\baton-jamf. Supported file pattern: go.mod
release / goreleaser-binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: apple-actions/import-codesign-certs@v1, aws-actions/configure-aws-credentials@v5, goreleaser/goreleaser-action@v6. 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/
release / goreleaser-binaries
Restore cache failed: Dependencies file is not found in /Users/runner/work/baton-jamf/baton-jamf. Supported file pattern: go.mod
release / goreleaser-binaries
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/
release / goreleaser-binaries
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/
release / goreleaser-binaries
Restore cache failed: Dependencies file is not found in /Users/runner/work/baton-jamf/baton-jamf. Supported file pattern: go.mod
release / record-lambda-registry
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@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/
release / record-connector-registry
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@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/
release / record-connector-registry
Restore cache failed: Dependencies file is not found in /home/runner/work/baton-jamf/baton-jamf. Supported file pattern: go.mod
release / verify-release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@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/
release / record-registry-api
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. 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/
release / record-registry-api
Restore cache failed: Dependencies file is not found in /home/runner/work/baton-jamf/baton-jamf. Supported file pattern: go.mod