Skip to content

Release pipeline (changesets, npm publish, binaries, provenance) #41

Open

Description

@joeblau

Description

GitHub Actions release workflow: changesets versioning, npm publish with provenance, attach compiled binaries + SKILL.md to GitHub releases.

Acceptance criteria

  • Tag -> publish automated
  • npm provenance enabled
  • Release notes generated

Dependencies

Size

M

Activity

  1. joeblau commented on Oct 16, 2026

    @joeblau
    ContributorAuthor

    Implementation merged in #50. Release publication now requires a push of a matching stable tag on reviewed main plus the publishing gate; manual dispatch never publishes. Four native candidates build/run, the exact tested npm archive is published with provenance, registry integrity/attestation and public npm/bunx installs are verified, and checksums/release assets are produced. Retry accepts an existing version only if its artifact integrity and provenance match.

    Candidate evidence: https://github.com/bloxwap/agent-cli/actions/runs/38948485326 . This does not claim publication. Keep the issue open until a real tagged publication passes registry/provenance/install checks and produces the GitHub release.

    Remaining setup: npm scope write access and initial token or trusted-publisher configuration, the npm-release environment/restrictions, and BLOXWAP_PUBLISH=1 after version review. The current changesets prepare0.2.0. GitHub rejected the repo Actions-PR setting with an organization-policy409; default version dispatch therefore uploads a validated reviewable patch, and automatic version-PR creation is optional after organization permission is resolved. Full steps are in docs/releases.md; no org policy, npm tag or publication was changed during this review.

  2. joeblau commented on Oct 16, 2026

    @joeblau
    ContributorAuthor

    Release preparation is complete in #51: main is now 0.2.0, pending changesets are consumed, and package/lock/changelog/skill/generated docs agree. The version workflow passed: https://github.com/bloxwap/agent-cli/actions/runs/38948917469 .

    The exact 0.2.0 candidate passed native executable and installed npm/bunx checks on Linux/macOS x64/ARM: https://github.com/bloxwap/agent-cli/actions/runs/38949351812 . The manual run correctly skipped publication and provides candidate download artifacts. PR #51 also passed CI, docs and the Node 22.12/24 macOS/Linux install matrix.

    The remaining criterion is the actual authenticated tagged npm release, its registry integrity/provenance/public installs, and GitHub release assets. The publishing gate is still unset and no version tag/package publication was created. Configure npm-release and npm authorization/trusted publishing before pushing the reviewed matching v0.2.0 tag. The separate Privy/testnet acceptance issues remain open as documented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions