Skip to content

fix(js): Republish npm package with correct multi-target dist (v0.1.4) #8

fix(js): Republish npm package with correct multi-target dist (v0.1.4)

fix(js): Republish npm package with correct multi-target dist (v0.1.4) #8

Triggered via push February 11, 2026 06:06
Status Success
Total duration 1m 44s
Artifacts

publish.yml

on: push
Publish to crates.io
47s
Publish to crates.io
Publish to PyPI
38s
Publish to PyPI
Publish to npm
44s
Publish to npm
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
Publish to npm
Process completed with exit code 1.
Publish to crates.io
Process completed with exit code 101.
Publish to crates.io
Process completed with exit code 101.
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.