From 9c4e39e2451a6e26c26aba5654d6d6b86cb37d86 Mon Sep 17 00:00:00 2001 From: Jon Ayers Date: Tue, 25 Nov 2025 19:37:17 -0500 Subject: [PATCH] fix: pin exact ghostty-web version in demo to avoid npx cache issues The npx cache locks transitive dependency resolutions in a package-lock.json. When @ghostty-web/demo depended on "ghostty-web": "next", npm would resolve the tag at install time and cache that resolution. Even when ghostty-web@next was updated, npx would reuse the stale cached version. By pinning to the exact version (e.g., "0.2.1-next.14.g"), each demo release is paired with its matching ghostty-web version, avoiding the cache staleness issue. --- .github/workflows/publish.yml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml index 8ad1d8f..a758f7f 100644 --- a/.github/workflows/publish.yml +++ b/.github/workflows/publish.yml @@ -209,13 +209,15 @@ jobs: if [[ "${{ steps.detect.outputs.is_tag }}" == "true" ]]; then NPM_VERSION="${BASE_VERSION}" NPM_TAG="latest" - GHOSTTY_WEB_DEP="latest" + # Pin to exact version to avoid npx cache issues with transitive deps + GHOSTTY_WEB_DEP="${BASE_VERSION}" else GIT_COMMIT=$(git rev-parse --short HEAD) COMMITS_SINCE_TAG=$(git rev-list --count HEAD ^$(git describe --tags --abbrev=0 2>/dev/null || echo HEAD) 2>/dev/null || echo "0") NPM_VERSION="${BASE_VERSION}-next.${COMMITS_SINCE_TAG}.g${GIT_COMMIT}" NPM_TAG="next" - GHOSTTY_WEB_DEP="next" + # Pin to exact version to avoid npx cache issues with transitive deps + GHOSTTY_WEB_DEP="${NPM_VERSION}" fi echo "version=${NPM_VERSION}" >> $GITHUB_OUTPUT