From 1673a2e2a1de5e7d8f33c0d1b17e4a1f689b182d Mon Sep 17 00:00:00 2001 From: Opita Code Dev Date: Wed, 22 Jul 2026 21:46:41 -0500 Subject: [PATCH] fix(ci): update publish-guard tarball glob after @opita -> @opitacode rename PR #3 renamed the package from @opita/ocais to @opitacode/ocais, but left the publish-guard workflow with the old hardcoded glob 'opita-ocais-*.tgz'. After npm pack now generates 'opitacode-ocais-3.0.0.tgz', the glob no longer matches and the CI fails at the 'Verify dist/ in tarball' step with: ls: cannot access 'opita-ocais-*.tgz': No such file or directory Update both globs (ls + artifact upload path) to the new package name. Add a NOTE comment so the next person who renames the package knows to update these globs too. Caught by: tag v3.0.0 push triggered publish-guard (run 29974882481), failed at 'Verify dist/ in tarball'. Local 132/132 tests + npm pack --dry-run confirm the new tarball is otherwise valid; only the glob is wrong. Refs: PR #3, SPEC-417 --- .github/workflows/publish-guard.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/.github/workflows/publish-guard.yml b/.github/workflows/publish-guard.yml index 32f4d7e..d0b0cde 100644 --- a/.github/workflows/publish-guard.yml +++ b/.github/workflows/publish-guard.yml @@ -35,9 +35,12 @@ jobs: run: npm pack - name: Verify dist/ in tarball + # NOTE: glob must match 'name' in package.json (npm pack uses that name + # for the tarball, e.g. opitacode-ocais-3.0.0.tgz). When the package + # is renamed, update both globs here. run: | set -e - TGZ=$(ls opita-ocais-*.tgz | head -n 1) + TGZ=$(ls opitacode-ocais-*.tgz | head -n 1) echo "Inspecting $TGZ" tar -tzf "$TGZ" if ! tar -tzf "$TGZ" | grep -q "package/dist/index.js"; then @@ -62,5 +65,5 @@ jobs: uses: actions/upload-artifact@v4 with: name: ocais-tarball - path: opita-ocais-*.tgz + path: opitacode-ocais-*.tgz if-no-files-found: error \ No newline at end of file