From 73d0dbb01cf0f99565fbeff307686f212873b330 Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Mon, 26 Oct 2026 19:41:20 -0700 Subject: [PATCH] chore(release): prepare 0.47.1 --- CHANGELOG.md | 8 ++++++-- docs/RELEASING.md | 8 ++++---- internal/cmd/VERSION | 2 +- 3 files changed, 11 insertions(+), 7 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 5633a6f01..127482bfd 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,8 +1,8 @@ # Changelog -## 0.47.1 - Unreleased +## 0.47.1 - 2026-10-26 -- Dependencies: update Google IAM, GAX, enterprise certificate support, Workers types, Wrangler, and oxlint-tsgolint while retaining Go 1.26 and the tracking worker’s 24-hour release cooldown. +**Highlights:** Preserve Gmail text direction and narrowed Calendar grants, fix headless Linux authentication, and reject compromised certificates in the tracking worker. - Gmail: give the author's own text its direction in HTML (`dir="auto"` on each line of converted plain text, once around given HTML, and on the signature) so right-to-left text reads correctly and English keeps its direction when a right-to-left reply quotes it; whole HTML documents go in as given. (#1255) — thanks @malob. @@ -10,6 +10,10 @@ - Auth: preserve Calendar read-only scope selections during automatic reauthorization instead of requesting previously granted broader access. (#1259) — thanks @pkyIntelligence. +- Security: update the tracking worker's workerd runtime to reject compromised eMudhra certificate chains. (#1264) — thanks @joshavant. + +- Dependencies: update Google IAM, GAX, enterprise certificate support, Workers types, Wrangler, and oxlint-tsgolint while retaining Go 1.26 and the tracking worker’s 24-hour release cooldown. + ## 0.47.0 - 2026-10-23 **Highlights:** Opt-in HTML Gmail bodies, selected search headers, and calendar settings updates, with OAuth error redaction and certificate trust fixes. diff --git a/docs/RELEASING.md b/docs/RELEASING.md index 541e5ad09..b0dbb2cc0 100644 --- a/docs/RELEASING.md +++ b/docs/RELEASING.md @@ -4,9 +4,9 @@ summary: "Unified GitHub Actions release process for GogCLI" # Releasing `gogcli` -Official releases run only through `.github/workflows/release-unified.yml`, which calls the fleet-standard `openclaw/release-workflows` Go CLI pipeline at `@v1`. Do not create or push release tags locally, and do not use local signing or notarization credentials. +Official releases run only through `.github/workflows/release-unified.yml`, which calls the fleet-standard `openclaw/release-workflows` Go CLI pipeline at `@v1`. Binary signing, notarization, and publication stay in Actions. After a successful dry run, create and verify the release tag with the fleet release SSH key before dispatching publication. -Release authorization is repository Actions write access combined with a protected, required-check-green `main` commit and the organization-scoped signing, notarization, and tap credentials. The shared workflow creates the immutable annotated tag; GogCLI intentionally has no separate local tag-signer authorization step. +Release authorization is repository Actions write access combined with a protected, required-check-green `main` commit and the organization-scoped signing, notarization, and tap credentials. The shared workflow reuses the immutable signed annotated tag, verifies its target, and never moves it. Use only the fleet release SSH key (fingerprint `SHA256:WmI9lVtd7F2c5XyRHbZVO3yYYJzwsSNzcZQMPT147HI`), not the local default signing key. Verify the signature before pushing; if the local allowlist does not trust that key, use a task-local allowed-signers file without changing trust settings. ## Prepare the release @@ -30,7 +30,7 @@ The caller preserves GogCLI's public artifact contract where applicable: ## Dispatch -From current protected `main`, dispatch the workflow with a SemVer version without a leading `v`: +First run the dry run described below on the protected release-prep merge commit. Once it succeeds, create the fleet-signed annotated `vX.Y.Z` tag at that exact commit, verify it, and push it. From current protected `main`, dispatch the workflow with a SemVer version without a leading `v`: ```sh gh workflow run release-unified.yml \ @@ -51,7 +51,7 @@ exact version match without the development suffix. ## Docker closeout -After the GitHub Release is public and its tag is verified, publish the Docker image separately unless an exact-tag Docker run has already succeeded. The unified workflow creates the tag with `GITHUB_TOKEN`, which does not trigger Docker's tag-push workflow. +After the GitHub Release is public and its tag is verified, publish the Docker image separately unless an exact-tag Docker run has already succeeded. A signed tag pushed by the release operator normally triggers Docker's tag-push workflow; tags created with `GITHUB_TOKEN` do not. ```sh gh workflow run docker.yml \ diff --git a/internal/cmd/VERSION b/internal/cmd/VERSION index a852ddd78..1a765e8a8 100644 --- a/internal/cmd/VERSION +++ b/internal/cmd/VERSION @@ -1 +1 @@ -v0.47.0-dev +v0.47.1