From a7699c00c9abbe5836c74d46f95dbeedc7823a81 Mon Sep 17 00:00:00 2001
From: latin-panda <66472237+latin-panda@users.noreply.github.com>
Date: Tue, 2 Dec 2025 16:03:39 +0700
Subject: [PATCH] fixes workflow

---
 .github/workflows/release.yml | 8 +++++++-
 README.md                     | 2 +-
 2 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 94bddea1a..7936c8774 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -17,12 +17,18 @@ jobs:
         uses: actions/setup-node@v4
         with:
           registry-url: "https://registry.npmjs.org"
+      - name: Enable Corepack
+        run: corepack enable
+
+      - name: Get yarn cache directory path
+        id: yarn-cache-dir-path
+        run: echo "dir=$(yarn cache dir)" >> $GITHUB_OUTPUT
 
       - name: Cache Yarn dependencies
         uses: actions/cache@v4
         with:
           path: |
-            ~/.cache/yarn
+            ${{ steps.yarn-cache-dir-path.outputs.dir }}
             **/node_modules
           key: yarn-${{ runner.os }}-${{ hashFiles('yarn.lock') }}
           restore-keys: |
diff --git a/README.md b/README.md
index c2594a5f2..57f5e3c0d 100644
--- a/README.md
+++ b/README.md
@@ -507,5 +507,5 @@ If you'd like to try the functionality available on `main`, see the preview [on
 1. Run `yarn changeset version` to generate changelog files and version bumps from the changeset files
 1. Run `yarn install` to update yarn.lock with the new versions
 1. Verify that the changelogs look good, commit changes, open a PR, merge the PR
-1. Push tags for each package in the format `package@x.x.x`. A Github action will publish the packages on NPM
+1. Push tags for each package in the format `@getodk/<package>@x.x.x`. A Github action will publish the packages on NPM
 1. Update dependencies to kick off the new release cycle. We do this so that dependency updates get verified implicitly during development.