Deploying to api, on staging #2615
deploy.yml
on: workflow_dispatch
prepare-matrix
3s
Matrix: run-clickhouse-migrations
Matrix: build
Matrix: deploy
sync_novu_state
6s
webhook_notification
Linear Release (Cloud)
27s
TesterArmy Staging Regression
4s
TesterArmy Production Regression
Matrix: new_relic_release
Matrix: sentry_release
Annotations
23 warnings
|
run-clickhouse-migrations (staging-eu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, novuhq/clickhouse-cloud-whitelist-ip-action@7594062e821f1f28af7673bf82e4df9ca2e78636. Actions will be forced to run with Node.js 24 by *** 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 ***, 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 (api)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, aws-actions/configure-aws-credentials@7474bc4690e29a8392af63c5b98e7449536d5c3a. 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/
|
|
deploy (staging-eu, api-cluster, api-internal-container, api-internal-service, api-internal-task,...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/amazon-ecs-deploy-task-definition@3e7310352de91b71a906e60c22af629577546002, aws-actions/amazon-ecs-render-task-definition@39c13cf530718ffeb524ec8ee0c15882bcb13842, aws-actions/configure-aws-credentials@7474bc4690e29a8392af63c5b98e7449536d5c3a. 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/
|
|
deploy (staging-eu, api-cluster, api-internal-container, api-internal-service, api-internal-task,...
Ignoring property 'registeredBy' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
deploy (staging-eu, api-cluster, api-internal-container, api-internal-service, api-internal-task,...
Ignoring property 'registeredAt' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
deploy (staging-eu, api-cluster, api-internal-container, api-internal-service, api-internal-task,...
Ignoring property 'status' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
deploy (staging-eu, api-cluster, api-internal-container, api-internal-service, api-internal-task,...
Ignoring property 'revision' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
deploy (staging-eu, api-cluster, api-internal-container, api-internal-service, api-internal-task,...
Ignoring property 'requiresAttributes' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
deploy (staging-eu, api-cluster, api-internal-container, api-internal-service, api-internal-task,...
Ignoring property 'taskDefinitionArn' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
deploy (staging-eu, api-cluster, api-internal-container, api-internal-service, api-internal-task,...
Ignoring property 'compatibilities' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
deploy (staging-eu, api-cluster, api-container, api-service, api-task, api)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/amazon-ecs-deploy-task-definition@3e7310352de91b71a906e60c22af629577546002, aws-actions/amazon-ecs-render-task-definition@39c13cf530718ffeb524ec8ee0c15882bcb13842, aws-actions/configure-aws-credentials@7474bc4690e29a8392af63c5b98e7449536d5c3a. 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/
|
|
deploy (staging-eu, api-cluster, api-container, api-service, api-task, api)
Ignoring property 'registeredBy' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
deploy (staging-eu, api-cluster, api-container, api-service, api-task, api)
Ignoring property 'registeredAt' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
deploy (staging-eu, api-cluster, api-container, api-service, api-task, api)
Ignoring property 'status' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
deploy (staging-eu, api-cluster, api-container, api-service, api-task, api)
Ignoring property 'revision' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
deploy (staging-eu, api-cluster, api-container, api-service, api-task, api)
Ignoring property 'requiresAttributes' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
deploy (staging-eu, api-cluster, api-container, api-service, api-task, api)
Ignoring property 'taskDefinitionArn' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
deploy (staging-eu, api-cluster, api-container, api-service, api-task, api)
Ignoring property 'compatibilities' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
sync_novu_state
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: novuhq/actions-novu-sync@dceec32b0c93c5d7f741e38094204fd5ebd9f308. 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/
|
|
sentry_release (api)
Input 'version_prefix' has been deprecated with message: Deprecated: Use "release_prefix" instead.
|
|
sentry_release (api)
Input 'version' has been deprecated with message: Deprecated: Use "release" instead.
|
|
sentry_release (api)
Input 'version_prefix' has been deprecated with message: Deprecated: Use "release_prefix" instead.
|
|
sentry_release (api)
Input 'version' has been deprecated with message: Deprecated: Use "release" instead.
|