Add lockfile freshness validation to plugin-ci workflow

When pnpm-lock.yaml has overrides section, validate that lockfile is fresh before install. If stale (detected via CONFIG_MISMATCH/EBADLOCKFILE/ERR_PNPM_LOCKFILE), fail with clear error message suggesting 'pnpm install' to regenerate. Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-05-12 22:29:12 +00:00
parent d2f1e497ef
commit 1c2b97d41d
1 changed files with 28 additions and 0 deletions
@@ -113,6 +113,34 @@ jobs:
          restore-keys: |
            ${{ runner.os }}-pnpm-
      - name: Validate pnpm lockfile freshness
        if: steps.pkg-manager.outputs.manager == 'pnpm'
        run: |
          if [ ! -f "pnpm-lock.yaml" ]; then
            echo "No pnpm-lock.yaml found, skipping lockfile freshness check"
            exit 0
          fi
          if ! grep -q 'overrides:' pnpm-lock.yaml 2>/dev/null; then
            echo "No overrides section in pnpm-lock.yaml, skipping lockfile freshness check"
            exit 0
          fi
          echo "Detected pnpm-lock.yaml with overrides section. Checking lockfile freshness..."
          ERR_FILE=$(mktemp)
          if pnpm install --frozen-lockfile 2>&1 | tee "$ERR_FILE"; then
            echo "Lockfile is fresh."
          else
            if grep -q "CONFIG_MISMATCH\|EBADLOCKFILE\|ERR_PNPM_LOCKFILE" "$ERR_FILE"; then
              echo ""
              echo "::error::pnpm-lock.yaml is out of sync with package.json overrides."
              echo "::error::This typically happens when transitive dependencies change but the lockfile wasn't regenerated."
              echo "::error::Run 'pnpm install' to regenerate the lockfile and commit the updated pnpm-lock.yaml."
              rm -f "$ERR_FILE"
              exit 1
            fi
            rm -f "$ERR_FILE"
            echo "::warning::Install failed with a different error. Will retry in the Install dependencies step."
          fi
      - name: Install dependencies
        run: |
          max_attempts=3