Skip to content

fix: publish mabr tarball from workspace path - #21

Merged
kkroo merged 1 commit into
mainfrom
codex/fix-mabr-publish-path
Oct 25, 2026
Merged

kkroo merged 1 commit into
mainfrom
codex/fix-mabr-publish-path

Conversation

@kkroo

@kkroo kkroo commented Oct 25, 2026

Copy link
Copy Markdown
Contributor

npm treats the unprefixed npm-packages-mabr path as a git package URL. Prefix the artifact with ./, matching the other publish jobs, so the mabr-route-proxy tag can publish through npm trusted publishing.

Checks: git diff --check.

@allyblockcast allyblockcast Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ally — Consolidated PR Review

Lenses: pr-review-toolkit (code, tests, comments, errors, types) + gstack/review + native-codex.
Reviewed head: b20ed9c

Looks good. npm reads the bare npm-packages-mabr/blockcast-mabr-route-proxy-*.tgz as a <owner>/<repo> GitHub shorthand, so it tries to fetch a git package. Adding ./ forces a local file path. The change is now byte-for-byte consistent with the three sibling publish steps (.github/workflows/publish-npm.yml:435, :438, :478). The artifact is downloaded to path: npm-packages-mabr in the workspace root, so the relative path resolves. The earlier version-assertion step uses the glob inside tar/echo, which are plain file paths, so it is unaffected.

Critical Issues (0)

Important Issues (0)

Suggestions (0)

Strengths

  • A minimal, root-cause fix that matches the established pattern in the same file.

Recommended Action

  1. No blocking changes requested.
  2. Merge once the remaining required CI checks finish green.

@kkroo
kkroo merged commit 0bafe11 into main Oct 25, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant