Skip to content

chore(integrations): Halting events to be logged as warning #197072

chore(integrations): Halting events to be logged as warning

chore(integrations): Halting events to be logged as warning #197072

Triggered via pull request April 15, 2026 20:14
Status Success
Total duration 1m 22s
Artifacts

openapi-diff.yml

on: pull_request
(Optional) Shows the difference between the prod and dev schema
1m 18s
(Optional) Shows the difference between the prod and dev schema
Fit to window
Zoom out
Zoom in

Annotations

1 warning
(Optional) Shows the difference between the prod and dev schema
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332, actions/setup-node@1e60f620b9541d16bece96c5465dc8ee9832be0b, actions/setup-python@0a5c61591373683505ea898e09a3ea4f39ef2b9c, astral-sh/setup-uv@884ad927a57e558e7a70b92f2bccf9198a4be546, dorny/paths-filter@0bc4621a3135347011ad047f9ecf449bf72ce2bd. 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/