Repository navigation
SkillWeave v1.5.4
·
403 commits
to main
since this release
The path that publishes a tagged release to the Capacium Exchange was wired for
Trusted Publishing but never asked for a token, so every tag since v1.3.12
reached the CLI with an empty credential and refused. This release turns that
path on. No runtime or skill code changes.
Fixed
- The Capacium publication step now requests a short-lived publish token through
OIDC (id-token: writeplususe_oidc: true) instead of arriving with an
emptyCAPACIUM_API_TOKEN. No long-lived Capacium secret is stored in the
repository; the Exchange derives the publisher owner from the OIDC claims and
issues a token scoped to exactly that owner and repository.
Changed
- The version-sync helper fetched by the release gate is pinned to ops-engine
v3.4.2, the same release the release workflow installs as its engine, so the
repository names one ops-engine version rather than two. The helper is
byte-identical acrossv3.0.0,v3.4.0andv3.4.2, so the gate's verdict is
unchanged. - The
check-manifestdiagnostic output is English, matching the rest of the
repository's tracked files. Only strings moved; its exit-code contract is
unchanged.
Upgrade
pip install --upgrade skillweave. src/ and skills/ are identical to 1.5.3,
so nothing you call changes.
Full changelog: CHANGELOG.md · Diff: v1.5.3...v1.5.4