chore: update deno.lock and freeze install during build #57119
d-gubertci.yml
on: pull_request
⚙️ Variables Setup
12s
Matrix: 🔎 Code Check / code-check
Waiting for pending jobs
Matrix: build
🔨 Test Storybook
/
Test Storybook
Matrix: 🚢 Build Docker
Matrix: 🔨 Test API (EE) / test
Waiting for pending jobs
Matrix: 🔨 Test API Livechat (EE) / test
Waiting for pending jobs
Matrix: 🔨 Test UI (EE) / test
Waiting for pending jobs
Matrix: 🔨 Test API Livechat (CE) / test
Waiting for pending jobs
Matrix: 🔨 Test API (CE) / test
Waiting for pending jobs
Matrix: 🔨 Test UI (CE) / test
Waiting for pending jobs
📦 Track Image Sizes
0s
📊 Report Coverage
0s
✅ Tests Done
2s
🚀 Notify external services
0s
Update Version Durability
/
update-versions
Annotations
4 errors and 1 warning
|
📦 Build Packages
Canceling since a higher priority waiting request for CI-chore/update-deno-lock exists
|
|
📦 Build Packages
The operation was canceled.
|
|
CI
Canceling since a higher priority waiting request for CI-chore/update-deno-lock exists
|
|
✅ Tests Done
Process completed with exit code 1.
|
|
📦 Build Packages
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, denoland/setup-deno@v1, rharkor/caching-for-turbo@v1.8. 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/
|