Skip to content

Cut v1.1.0 - #27

Merged
dolph merged 1 commit into
mainfrom
claude/cut-v1.1.0
Apr 27, 2026
Merged

Cut v1.1.0#27
dolph merged 1 commit into
mainfrom
claude/cut-v1.1.0

Conversation

@dolph

@dolph dolph commented Apr 27, 2026

Copy link
Copy Markdown
Owner

Promotes the [Unreleased] section in CHANGELOG.md to [1.1.0] - 2026-04-27 and adds a fresh empty [Unreleased] above it. Updates the compare-link footnotes so [Unreleased] now compares HEAD against v1.1.0 and the new [1.1.0] entry compares v1.0.2...v1.1.0.

Why 1.1.0 (not 1.0.3 or 2.0.0)

Per SemVer, this is a MINOR bump from 1.0.x:

  • Added cache_ttl config field — backwards-compatible (omitting it preserves the new default behavior).
  • Security change behavior — cache entries now expire (previously: never). This is the intent of fixing cache.go: cached responses never expire, so revoked SSH keys keep authenticating indefinitely #3 and is the right opt-out-not-opt-in default for a tool in the authentication path; defaulting to cache_ttl: 0 (= retain old behavior) would have shipped the security bug forever. Operators who actively want the old behavior can set cache_ttl to something very large.
  • No public API removed; no breaking source-level change.

A 1.0.3 PATCH bump would understate the new feature (cache_ttl); a 2.0.0 MAJOR bump would overstate the disruption (no API was removed, just runtime behavior tightened in the security-correct direction).

v1.1.0 contents

Already populated in [Unreleased] before this PR — this commit just renames the heading and updates compare links.

  • Added: cache_ttl config field; sha256 release-asset publication and install.sh verification; shellcheck CI.
  • Changed: install.sh download path uses curl -fLO + checksum verification.
  • Fixed: HTTP fetch errors no longer terminate the process.
  • Security: cache entries now expire so revoked keys actually stop authenticating.

What happens after this merges

The release workflow (.github/workflows/go.yml) triggers on tags: v*. Once this PR is on main, push the v1.1.0 tag — the workflow builds, generates ussher.sha256, and uploads both as v1.1.0 release assets with CHANGELOG.md as the release body. CLI for that step is in the chat reply that opened this PR.

Test plan

  • CHANGELOG renders cleanly; compare links resolve (will be live once the tag exists).
  • CI shellcheck + build jobs both green on the PR.
  • (post-merge) git push origin v1.1.0 runs the release workflow, which produces both ussher and ussher.sha256 on the v1.1.0 release page with the CHANGELOG as body.

https://claude.ai/code/session_013HnepY8MhhxrJJjE5ysW47


Generated by Claude Code

Renames the [Unreleased] section to [1.1.0] - 2026-04-27 and adds a
fresh [Unreleased] above it. Updates the compare-link footnotes so
[Unreleased] now compares HEAD against v1.1.0 and the new [1.1.0]
entry compares v1.0.2...v1.1.0.

The v1.1.0 contents (already populated in [Unreleased] before this
commit):

- Added: cache_ttl config, sha256 release-asset publication +
  install.sh verification, shellcheck CI.
- Changed: install.sh download path now uses curl -fLO + checksum
  verification.
- Fixed: HTTP fetch errors no longer terminate the process.
- Security: cache entries now expire so revoked keys actually stop
  authenticating.

Per SemVer, this is a MINOR bump from 1.0.x: cache_ttl is a new
backwards-compatible config field; the cache-expiry behavior change
from "never expires" to "expires every 5m by default" is the
*intent* of the security fix and is the right opt-out-not-opt-in
default for an authentication-path tool. No public API removed; no
breaking source-level change.

Once this lands on main, push the v1.1.0 tag to trigger the release
workflow (which will build the binary, generate ussher.sha256, and
publish both as the v1.1.0 release assets with CHANGELOG.md as the
release body).
@dolph
dolph merged commit 14fa050 into main Apr 27, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants