You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Release 0.8.0, the first version under the Kalpack name
Version, not 0.7.0. Kalpack emits KP-N extension identifiers in
ConformanceReport.extensions where annpack 0.7.0 emitted ANN-N, so the same
number would name two different output contracts. The bootstrap publish of
@kalpack/node@0.7.0 -- needed to bring the npm package into existence before
a trusted publisher could be attached to it -- also makes 0.7.0 unusable:
the release workflow skips npm when the version already exists, so tagging
v0.7.0 would ship binaries and PyPI while silently publishing nothing to
npm.
The three declarations the release gates compare against the tag are
Cargo.toml, bindings/python/pyproject.toml and bindings/node/package.json.
The README install paths become true at this tag rather than aspirational:
the asset URL names v0.8.0 instead of a placeholder, and `cargo install`
regains --tag now that a release carrying the kalpack crate name exists.
check-world-demo no longer pins the version inside the candidacy badge. The
claim it exists to test is candidacy; the version is already owned by
check-doc-consistency, which compares the badge against Cargo.toml and
caught this bump's one missed reference. Two gates asserting the same fact
meant a release bump failed one of them for an unrelated reason.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>