Skip to content

Fix npm publish path ambiguity and add one-off release recovery workflow - #144

Merged
philippjfr merged 1 commit into
mainfrom
fix/release-npm-publish
Aug 20, 2026
Merged

philippjfr merged 1 commit into
mainfrom
fix/release-npm-publish

Conversation

@philippjfr

Copy link
Copy Markdown
Contributor

npm parsed the bare "dist/*.tgz" arg as a GitHub shorthand spec instead of a local path, breaking the 1.8.0 npm publish. Prefix with ./ to disambiguate, and add finish-release.yml to retry the npm publish and GitHub release for 1.8.0 by reusing the already-built artifacts, without re-triggering the (already successful) PyPI/conda publishes.

npm parsed the bare "dist/*.tgz" arg as a GitHub shorthand spec instead
of a local path, breaking the 1.8.0 npm publish. Prefix with ./ to
disambiguate, and add finish-release.yml to retry the npm publish and
GitHub release for 1.8.0 by reusing the already-built artifacts,
without re-triggering the (already successful) PyPI/conda publishes.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@philippjfr
philippjfr merged commit fb7b19b into main Aug 20, 2026
4 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