Skip to content

Tags

Tags

v1.13.0

Toggle v1.13.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore(release): 1.13.0 (#443)

v1.12.2

Toggle v1.12.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore(release): 1.12.2 (#439)

v1.12.1

Toggle v1.12.1's commit message
chore: set 1.12.1 release date

v1.12.0

Toggle v1.12.0's commit message
chore: release 1.12.0

v1.12.0-beta.1

Toggle v1.12.0-beta.1's commit message
chore: release 1.12.0-beta.1

v1.12.0-beta.0

Toggle v1.12.0-beta.0's commit message
chore: release 1.12.0-beta.0

v1.11.0

Toggle v1.11.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore(release): 1.11.0 (#391)

v1.10.1

Toggle v1.10.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore(release): 1.10.1 (#357)

v1.10.0

Toggle v1.10.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore(release): 1.10.0 (#341)

* chore(release): 1.10.0

* ci: publish to npm with provenance

Attaches a signed attestation linking each published tarball to the exact
commit and workflow run that built it, which npm surfaces as a Provenance
badge on the package page.

The value is not that it prevents a bad publish. It is that it makes one
visible: a version pushed from a stolen NPM_TOKEN on someone's laptop
carries no attestation, and the gap is public.

Needs id-token: write, since the attestation is signed with a GitHub OIDC
token. Without that permission the publish fails outright rather than
quietly shipping unsigned, which is the behaviour we want.

v1.9.0

Toggle v1.9.0's commit message
chore(release): 1.9.0