Problem
Tag v0.1.0 exists, but the repository has no GitHub release and therefore no supported portable artifactserver archive. The tagged release workflow run failed in the npm-adapter publication gate:
The workflow had already assembled the portable Node archive, but the release was correctly withheld because the full release gate did not pass. Downstream consumers must not replace it with a source-checkout installation or manually publish unverified assets.
Outcome
Restore the npm publication credentials or trusted-publishing configuration, rerun the tagged release pipeline, and publish a GitHub release whose checksums and attestations include the portable artifact-server-0.1.0-node.tar.gz asset.
Acceptance
- The tagged release workflow passes all release gates.
- GitHub release
v0.1.0 exists with the portable CLI archive, manifest/SBOM, and SHA256SUMS.
- A clean environment with Node
>=24.12.0 can verify the checksum, extract the archive, and run artifactserver --version without a source checkout.
Problem
Tag
v0.1.0exists, but the repository has no GitHub release and therefore no supported portableartifactserverarchive. The tagged release workflow run failed in the npm-adapter publication gate:@plannotator/artifact-server-pi@0.1.0returned npmE404/ permission denial.The workflow had already assembled the portable Node archive, but the release was correctly withheld because the full release gate did not pass. Downstream consumers must not replace it with a source-checkout installation or manually publish unverified assets.
Outcome
Restore the npm publication credentials or trusted-publishing configuration, rerun the tagged release pipeline, and publish a GitHub release whose checksums and attestations include the portable
artifact-server-0.1.0-node.tar.gzasset.Acceptance
v0.1.0exists with the portable CLI archive, manifest/SBOM, andSHA256SUMS.>=24.12.0can verify the checksum, extract the archive, and runartifactserver --versionwithout a source checkout.