From 55a2e4d31b5c0539d0d8bb0e84d0b4e336cb7b64 Mon Sep 17 00:00:00 2001 From: merencia Date: Thu, 18 Jun 2026 14:43:22 -0300 Subject: [PATCH] chore: pin Yarn via corepack in release and deploy workflows The release and deploy-website workflows used threeal/setup-yarn-action with version: berry, which downloads the latest Yarn (4.17.0) and ignores the packageManager: yarn@4.14.1 pin. The newer Yarn migrates the lockfile metadata from 9 to 10, so the install fails with YN0028 (lockfile would be modified), breaking the release of the previously merged change. Use corepack with the pinned version, matching the build/test setup action. deploy-website now installs deps explicitly since the removed action handled it. --- .github/workflows/deploy-website.yml | 10 +++++----- .github/workflows/release.yml | 9 +++------ 2 files changed, 8 insertions(+), 11 deletions(-) diff --git a/.github/workflows/deploy-website.yml b/.github/workflows/deploy-website.yml index 29b5f0bd..ac152559 100644 --- a/.github/workflows/deploy-website.yml +++ b/.github/workflows/deploy-website.yml @@ -30,11 +30,11 @@ jobs: - name: Setup Pages uses: actions/configure-pages@v4 - - name: Setup Latest Yarn - uses: threeal/setup-yarn-action@v2.0.0 - with: - version: berry - cache: false + - name: Enable Corepack + run: corepack enable + + - name: Install dependencies + run: yarn install --immutable - name: Build project env: diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 99c9ab15..34104e2a 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -36,14 +36,11 @@ jobs: node-version: "22" registry-url: "https://registry.npmjs.org" - - name: Setup Latest Yarn - uses: threeal/setup-yarn-action@v2.0.0 - with: - version: berry - cache: false + - name: Enable Corepack + run: corepack enable - name: Install dependencies - run: yarn install + run: yarn install --immutable - name: Build run: yarn build