Skip to content

docs(changelog): v0.1.0 release notes#22

Merged
ironystock merged 1 commit into
mainfrom
chore/changelog-v0.1.0
Apr 29, 2026
Merged

docs(changelog): v0.1.0 release notes#22
ironystock merged 1 commit into
mainfrom
chore/changelog-v0.1.0

Conversation

@ironystock
Copy link
Copy Markdown
Contributor

@ironystock ironystock commented Apr 29, 2026

Summary

Adds `CHANGELOG.md` with v0.1.0 release notes ahead of the tag. Keep a Changelog format, semver. Doc-only — no build / test / release impact.

Why now

Phase 5 of the polish sprint is the v0.1.0 tag. `goreleaser` will reference release notes from the changelog (or the tag annotation, depending on config) — having the notes in-tree before tagging means strangers landing on the GitHub Releases page get something coherent rather than auto-generated commit-list noise.

Coverage

The v0.1.0 entry summarizes everything user-visible from the sprint:

  • 13-command surface (pair, add, recall, search, list, get, rm, namespaces, connections, audit, keys, import, export, config, completion)
  • Output presentation (fang help, lipgloss tables, tabwriter fallback, `--json` mode)
  • Leveled logging (`-v` / `--verbose` / `--quiet` via charmbracelet/log)
  • Huh-styled pair prompts in TTY, bufio fallback otherwise
  • API key + URL preflight with actionable error
  • Cross-platform binaries + Homebrew + Scoop + styled install.sh
  • rememberize-bundle Claude Code skill

Plus:

  • Notes for users — flags the `-v` vs `--version` rebinding (so anyone scripting against the old behavior knows).
  • Known limitations — Windows ARM64 not published, macOS not notarized, F18 (Windows per-invocation latency on the roadmap).

Verification

  • File renders cleanly on GitHub's markdown preview.
  • Compare-link footer URLs point at `captured-ventures/rememberize-cli` correctly.

Test plan

  • CI green (only `Mod Tidy Drift`, `GoReleaser Config`, `Lint` would touch this kind of change anyway; tests don't read the file).
  • After merge, you tag `v0.1.0` per the Phase 5 checklist and goreleaser fires.

Pre-tag checklist (carry-forward, for after this merges)

```

  1. Confirm main is green
  2. Smoke build from main: ./bin/rememberize --version → dev-
  3. Tag: git tag -a v0.1.0 -m "v0.1.0 — first public release"
    git push origin v0.1.0
  4. Watch the Release workflow:
    • GitHub Releases page (5 platform binaries)
    • captured-ventures/homebrew-rememberize push
    • captured-ventures/scoop-rememberize push
  5. Verify each install path:
    curl -sSL https://rememberize.app/install.sh | sh
    brew tap captured-ventures/rememberize && brew install rememberize
    scoop bucket add rememberize https://github.com/captured-ventures/scoop-rememberize && scoop install rememberize
    ```

🤖 Generated with Claude Code


View in Codesmith
Need help on this PR? Tag @codesmith with what you need.

  • Let Codesmith autofix CI failures and bot reviews

First entry. Keep a Changelog format, semver. Summarises the
sprint's user-visible additions in terms a stranger landing on
the GitHub Releases page can act on:

  - 13-command surface (pair, add, recall, search, list, get, rm,
    namespaces, connections, audit, keys, import, export, config,
    completion)
  - Output presentation (fang help, lipgloss tables, tabwriter
    fallback, --json mode)
  - Leveled logging (-v / --verbose / --quiet via charmbracelet/log)
  - Huh-styled pair prompts in TTY, bufio fallback otherwise
  - API key + URL preflight with actionable error
  - Cross-platform binaries + Homebrew + Scoop + styled install.sh
  - rememberize-bundle Claude Code skill

Plus a short "Notes for users" section flagging the -v vs --version
flag rebinding, and "Known limitations" covering Windows arm64,
macOS notarization, and F18 (Windows per-invocation latency).

CHANGELOG.md is doc-only; doesn't affect build/test/release.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@ironystock ironystock merged commit d3e6c4f into main Apr 29, 2026
7 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.

1 participant