Skip to content

v0.4.2: Release plumbing on release-please

Choose a tag to compare

View all tags
@github-actions github-actions released this 12 Jun 12:16
v0.4.2
c5eca83
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

A maintenance release that swaps the release machinery over to release-please while keeping Communique as the changelog author. No CLI, JSON envelope, snapshot, recording, or export behavior changes — the published npm tarball and GitHub Release artifacts are produced by the same tag-driven release.yml pipeline as v0.4.1.

Changed

  • Release flow moved to release-please + Communique (#143 by @ThomasK33). The previous [Unreleased] bot-PR workflow, the release/* changelog workflow, and the local release:prep / release:finalize scripts are retired. A single standing chore(release): <version> PR is now maintained on every push to main; merging it tags v<version>, creates the GitHub Release, and dispatches the existing publish pipeline. Version selection follows Conventional Commits with bump-minor-pre-major + bump-patch-for-minor-pre-major to match the pre-1.0 cadence (breaking → minor, feat/fix → patch); Release-As: footers still override.
  • CHANGELOG headings drop the v prefix. New sections are written as ## [0.4.2] - <date> instead of ## [v0.4.2] - ...; release-please's PR-body parser requires a digit immediately after the bracket, so a leading v would cause the merge to produce no release. The historical ## [v0.4.1] entry is left untouched.
  • ## [Unreleased] anchor preserved. A custom node-strategy updater inserts new release sections below the [Unreleased] heading (release-please's stock updater would insert above it) and clears any staged draft once it has been folded into the generated notes. Maintainers can continue to stage draft wording under [Unreleased] and Communique will reconcile it into the next release.
  • ADR 0009 records the decision; ADR 0002 (release-it for release prep) is superseded, and docs/RELEASE-PROCESS.md has been rewritten for the new flow.

Notes for maintainers

  • Requires the existing ANTHROPIC_API_KEY secret (or OPENAI_API_KEY + COMMUNIQUE_MODEL var) — same contract as the retired workflows.
  • Any leftover automation/update-unreleased-changelog PR should be closed; its workflow no longer exists.

Full Changelog: v0.4.1...v0.4.2

Install from npm once the trusted publish job for this workflow completes:

npm install -g "agent-tty@0.4.2"
agent-tty version --json

If you need a registry-independent fallback, install the verified tarball asset from this release directly:

VERSION=0.4.2
RELEASE_TAG=v0.4.2
TARBALL_URL=https://github.com/coder/agent-tty/releases/download/v0.4.2/agent-tty-0.4.2.tgz

npm install -g "$TARBALL_URL"
agent-tty version --json

For private releases or environments that require authenticated downloads, fetch the asset first and then install locally:

gh release download "v0.4.2" --repo "coder/agent-tty" --pattern "agent-tty-0.4.2.tgz"
npm install -g "./agent-tty-0.4.2.tgz"
agent-tty version --json

SHA-256 checksum: cfaf6bdd998a43722082cb79a8052164ccae24b3e34f3bfa036404ab541857e5 (see agent-tty-0.4.2.tgz.sha256 for the portable checksum file).

This workflow prepares one verified tarball and reuses it across GitHub Release assets and npm publishing instead of rebuilding it.

Contributors

ThomasK33
Assets 4
Loading