Skip to content

Fold finish release into main release flow - #145

Merged
philippjfr merged 2 commits into
mainfrom
fix/release-npm-publish
Aug 20, 2026
Merged

philippjfr merged 2 commits into
mainfrom
fix/release-npm-publish

Conversation

@philippjfr

Copy link
Copy Markdown
Contributor

NPM releases have to happen on the main release flow.

philippjfr and others added 2 commits August 20, 2026 09:45
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>
npm's trusted publisher for @bokeh/ipywidgets_bokeh is bound to the
release.yml workflow filename, so dispatching a separate workflow file
got a 404 from npm's OIDC check even though the package exists.
Instead, add a workflow_dispatch input on release.yml itself that
skips build/PyPI/conda and reuses artifacts from a prior run, so the
npm publish (and GitHub release) retry runs under the same trusted
workflow.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@philippjfr
philippjfr merged commit e0fd231 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