Skip to content

v0.1.1

  • v0.1.1
  • a5240d3

  • Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature.
    GPG key ID: B5690EEEBB952194
    Verified
    Learn about vigilant mode

  • Choose a tag to compare

    View all tags
v0.1.1: chore(release): 0.1.1 — release-pipeline hardening (#305)
  • v0.1.1
  • a5240d3

  • Choose a tag to compare

    View all tags

  • Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature.
    GPG key ID: B5690EEEBB952194
    Verified
    Learn about vigilant mode
@stevekinney stevekinney tagged this 06 Jun 02:23 
Patch release; no library/runtime changes. Bundles the post-0.1.0
follow-ups:

- verify-release-version.ts: prefer TAG_NAME over GITHUB_REF_NAME so a
  workflow_dispatch release passes the version check without a tag-ref
  workaround (GITHUB_REF_NAME is the branch on dispatch, not the tag).
- Bump Bun 1.3.2 -> 1.3.13 in release.yaml and release-manual.yaml,
  aligning with CI's BUN_VERSION and fixing the dequal bundler
  'Multiple files share the same output path' collision that kept
  release.yaml's validate step red on main.
- Reconcile provenance: NPM_CONFIG_PROVENANCE='false' in both release
  workflows to match package.json#publishConfig.provenance=false. npm
  publish runs under Bun's BoringSSL, which fails provenance signing
  (ERR_OSSL_NO_DEFAULT_DIGEST). Both sources agree so config precedence
  can't reintroduce the failure.

components.json + CHANGELOG.md regenerated by changeset version +
components:generate.
Assets 2
Loading