Bump urllib3 from 2.6.0 to 2.6.3 in /flytectl/docs #7509
Sovietacedchecks.yml
on: pull_request
flyteadmin integration tests image
/
build_docker
Dry Run Goreleaser
1m 2s
Test Getting started
1m 15s
Matrix: Build Images / Build & Push Image
Matrix: Check Go Generate
Matrix: Lint
Matrix: Unit Tests
Matrix: Integration Test
Waiting for pending jobs
Annotations
81 errors and 54 warnings
|
Dry Run Goreleaser
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Dry Run Goreleaser
The operation was canceled.
|
|
Build Images / Build & Push Image (datacatalog) / Push to Github Registry
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Build Images / Build & Push Image (datacatalog) / Push to Github Registry
The operation was canceled.
|
|
Build Images / Build & Push Image (flyteadmin) / Push to Github Registry
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Build Images / Build & Push Image (flyteadmin) / Push to Github Registry
The operation was canceled.
|
|
Unit Tests (datacatalog) / Run Unit Test
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Unit Tests (datacatalog) / Run Unit Test
The operation was canceled.
|
|
Test Getting started
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Test Getting started
The operation was canceled.
|
|
Lint (datacatalog) / Run Lint
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Lint (datacatalog) / Run Lint
The operation was canceled.
|
|
Check Go Generate (flytectl) / Go Generate
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Lint (flyteidl) / Run Lint
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Lint (flyteidl) / Run Lint
The operation was canceled.
|
|
Check Go Generate (flytectl) / Go Generate
The operation was canceled.
|
|
flyteadmin integration tests image / build_docker
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
flyteadmin integration tests image / build_docker
The operation was canceled.
|
|
Unit Tests (flytectl) / Run Unit Test
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Unit Tests (flytectl) / Run Unit Test
The operation was canceled.
|
|
Unit Tests (flyteadmin) / Run Unit Test
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Unit Tests (flytecopilot) / Run Unit Test
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Unit Tests (flyteadmin) / Run Unit Test
The operation was canceled.
|
|
Unit Tests (flytecopilot) / Run Unit Test
The operation was canceled.
|
|
Lint (flytectl) / Run Lint
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Lint (flytectl) / Run Lint
The operation was canceled.
|
|
Check Go Generate (flytepropeller) / Go Generate
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Check Go Generate (flytecopilot) / Go Generate
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Lint (flyteadmin) / Run Lint
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Check Go Generate (flytecopilot) / Go Generate
The operation was canceled.
|
|
Check Go Generate (flytepropeller) / Go Generate
The operation was canceled.
|
|
Lint (flyteadmin) / Run Lint
The operation was canceled.
|
|
Lint (flytecopilot) / Run Lint
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Lint (flytecopilot) / Run Lint
The operation was canceled.
|
|
Lint (flytepropeller) / Run Lint
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Check Go Generate (datacatalog) / Go Generate
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Lint (flytepropeller) / Run Lint
The operation was canceled.
|
|
Check Go Generate (datacatalog) / Go Generate
The operation was canceled.
|
|
Lint (flyteplugins) / Run Lint
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Unit Tests (flyteplugins) / Run Unit Test
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Lint (flyteplugins) / Run Lint
The operation was canceled.
|
|
Unit Tests (flyteplugins) / Run Unit Test
The operation was canceled.
|
|
Check Go Generate (flyteadmin) / Go Generate
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Check Go Generate (flyteadmin) / Go Generate
The operation was canceled.
|
|
Lint (flytestdlib) / Run Lint
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Lint (flytestdlib) / Run Lint
The operation was canceled.
|
|
Unit Tests (flytepropeller) / Run Unit Test
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Unit Tests (flytepropeller) / Run Unit Test
The operation was canceled.
|
|
Unit Tests (flytestdlib) / Run Unit Test
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Unit Tests (flytestdlib) / Run Unit Test
The operation was canceled.
|
|
Build Images / Build & Push Image (flytescheduler) / Push to Github Registry
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Build Images / Build & Push Image (flytescheduler) / Push to Github Registry
The operation was canceled.
|
|
Build Images / Build & Push Image (flytecopilot) / Push to Github Registry
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Build Images / Build & Push Image (flytecopilot) / Push to Github Registry
The operation was canceled.
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Build Images / Build & Push Image (flytepropeller) / Push to Github Registry
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Build Images / Build & Push Image (flytepropeller) / Push to Github Registry
The operation was canceled.
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Components Checks
Canceling since a higher priority waiting request for Components Checks-6849 exists
|
|
Dry Run Goreleaser
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, goreleaser/goreleaser-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/
|
|
Dry Run Goreleaser
You are using 'latest' as default version. Will lock to '~> v1'.
|
|
Build Images / Build & Push Image (datacatalog) / Push to Github Registry
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/metadata-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@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/
|
|
Build Images / Build & Push Image (datacatalog) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (datacatalog) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (datacatalog) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (datacatalog) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (datacatalog) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flyteadmin) / Push to Github Registry
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/metadata-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@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/
|
|
Build Images / Build & Push Image (flyteadmin) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flyteadmin) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flyteadmin) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flyteadmin) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flyteadmin) / Push to Github Registry
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/
|
|
Unit Tests (datacatalog) / Run Unit Test
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@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/
|
|
Lint (datacatalog) / Run Lint
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@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/
|
|
Lint (flyteidl) / Run Lint
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@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/
|
|
Check Go Generate (flytectl) / Go Generate
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@v5, arduino/setup-protoc@v3, bufbuild/buf-setup-action@v1. 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/
|
|
flyteadmin integration tests image / build_docker
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@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/
|
|
flyteadmin integration tests image / build_docker
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/
|
|
Unit Tests (flytectl) / Run Unit Test
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@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/
|
|
Unit Tests (flyteadmin) / Run Unit Test
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@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/
|
|
Unit Tests (flytecopilot) / Run Unit Test
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@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/
|
|
Lint (flytectl) / Run Lint
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@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/
|
|
Check Go Generate (flytepropeller) / Go Generate
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@v5, arduino/setup-protoc@v3, bufbuild/buf-setup-action@v1. 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/
|
|
Check Go Generate (flytecopilot) / Go Generate
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@v5, arduino/setup-protoc@v3, bufbuild/buf-setup-action@v1. 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/
|
|
Lint (flyteadmin) / Run Lint
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@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/
|
|
Lint (flytecopilot) / Run Lint
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@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/
|
|
Lint (flytepropeller) / Run Lint
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@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/
|
|
Check Go Generate (datacatalog) / Go Generate
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@v5, arduino/setup-protoc@v3, bufbuild/buf-setup-action@v1. 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/
|
|
Lint (flyteplugins) / Run Lint
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@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/
|
|
Unit Tests (flyteplugins) / Run Unit Test
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@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/
|
|
Check Go Generate (flyteadmin) / Go Generate
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@v5, arduino/setup-protoc@v3, bufbuild/buf-setup-action@v1. 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/
|
|
Lint (flytestdlib) / Run Lint
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@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/
|
|
Unit Tests (flytepropeller) / Run Unit Test
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@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/
|
|
Unit Tests (flytestdlib) / Run Unit Test
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@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 Images / Build & Push Image (flytescheduler) / Push to Github Registry
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/metadata-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@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/
|
|
Build Images / Build & Push Image (flytescheduler) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flytescheduler) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flytescheduler) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flytescheduler) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flytescheduler) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flytecopilot) / Push to Github Registry
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/metadata-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@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/
|
|
Build Images / Build & Push Image (flytecopilot) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flytecopilot) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flytecopilot) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flytecopilot) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flytecopilot) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flytepropeller) / Push to Github Registry
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/metadata-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@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/
|
|
Build Images / Build & Push Image (flytepropeller) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flytepropeller) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flytepropeller) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flytepropeller) / Push to Github Registry
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/
|
|
Build Images / Build & Push Image (flytepropeller) / Push to Github Registry
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/
|