Repository navigation
fix(ci): update publish-guard tarball glob after @opita -> @opitacode rename - #4
Merged
Merged
Conversation
… 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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix the
publish-guardCI workflow after the package rename in PR #3 (@opita/ocais→@opitacode/ocais).The workflow had two hardcoded tarball globs (
opita-ocais-*.tgz) that no longer match the new package name. Tagv3.0.0triggered the CI, which failed at the "Verify dist/ in tarball" step with:(Confirmed in run #29974882481.)
Changes (1 file, 5 insertions, 2 deletions)
.github/workflows/publish-guard.yml:opita-ocais-*.tgz→opitacode-ocais-*.tgz(2 places:lsandupload-artifactpath)NOTEcomment warning that the glob must match thenameinpackage.jsonVerification
npm pack --dry-runconfirms the new tarball name isopitacode-ocais-3.0.0.tgzand contains all 4 critical files (dist/index.js,dist/index.d.ts,dist/lambda/sse-writer.js,dist/providers/openai-compatible.js).v3.0.0needs to be re-cut (delete + re-push) so the CI re-runs against the fixed workflow.Out of scope
v3.0.0(handled by the operator or a follow-up PR after merge)npm publishto npm (SPEC-417, separate workflow)Refs