maint: prepare 0.1.0 release packaging - #27
Merged
Merged
Conversation
Bump the workspace version from 0.1.0-alpha.1 to 0.1.0, consolidate CHANGELOG.md's Unreleased section into a dated 0.1.0 release covering PRs #19-#26, rewrite the README for a non-technical audience with technical depth moved to a "For developers" section, add a template Homebrew formula under packaging/homebrew/ for a future tap, and record the 0.1.0 pull-request sequence in docs/roadmap/. No tag, GitHub release, or publish step was performed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015LY7xtercMc3NtLeX2z4YV
Two review-only installation targets (Codex and Claude Code skills), not three. Also rename "local and hybrid retrieval" to its actual name, "exact and hybrid retrieval". Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015LY7xtercMc3NtLeX2z4YV
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Claim
Package the repository for its first release,
0.1.0, without performing the release itself. No tag was pushed, no GitHub release was created or published, and nothing was published to any registry (crates.io, Homebrew, npm, etc.). The user releases manually after this merges.What changed
Cargo.tomlworkspace version0.1.0-alpha.1→0.1.0(all 16 workspace crates inherit viaversion.workspace = true);Cargo.lockregenerated viacargo build --workspace --all-features.apps/macos/scripts/make-app-bundle.shalready setCFBundleShortVersionStringto0.1.0— verified consistent, left unchanged. Grepped the tree for remaining0.1.0-alphareferences: only two remain, both genuinely historical prose (docs/roadmap/release-0.1.0-pull-requests.md's "X → Y" bump note, and ADR 0008's "Through 0.1.0-alpha, evidence only enters the store..." describing pre-decision state) — left as-is.[Unreleased]into a new## [0.1.0] - 2026-07-17section, kept an empty[Unreleased]on top, and added entries for PRs merged since the changelog was written: fix: tighten retrieval CLI and ranking edge cases #19 (retrieval CLI/ranking fixes, Fixed), feat: add Claude Code installation target #21 (Claude Code install target), feat: add local model synthesis providers #22 (local synthesis providers — Ollama + OpenAI-compatible, loopback-default, token accounting, mutation/0.2 provenance), feat: add Pi and OpenCode adapters #23 (Pi + OpenCode adapters), feat: add macOS menu-bar experience #24 (macOS menu-bar experience, Added; WAL read-only fix, Fixed), feat: add watch mode and daemon lifecycle #25/fix: apply rustfmt to watch and daemon modules #26 (watch mode + daemon lifecycle; the fix: apply rustfmt to watch and daemon modules #26 fmt/clippy fix folds into the same entry as a no-semantic-change follow-up).packaging/homebrew/autophagy.rb— a CLI-only, build-from-source template formula (documented choice: the macOS app is a separate SwiftUI package, out of scope for a Homebrew CLI formula) with clearly markedPLACEHOLDER_URL/PLACEHOLDER_SHA256and a comment header explaining there is no tap yet. Addedpackaging/homebrew/README.mdwith step-by-step instructions for filling it in and standing up a tap after tagging. Verifiedruby -cpasses and thatautophagy --version(used in the formula'stest doblock) actually printsautophagy 0.1.0.Status: completemarkers, matching the existing roadmap style. Updateddocs/roadmap/alpha-pull-requests.md's closing "Release readiness" note (wasStatus: in progress, referencing an unpublished0.1.0-alpha.1) to point at the new doc and reflect completion.cp README.md LICENSE CHANGELOG.mdstep, and the app-bundle path are all still accurate. No changes needed.Evidence
mise run check(ci + docs + fmt + lint + test): exit 0.swift testinapps/macos: 36/36 tests passed (0 failures).ruby -c packaging/homebrew/autophagy.rb: Syntax OK.grep -rn "0.1.0-alpha"across*.rs/*.toml/*.md/*.swift/*.sh/*.lock: only the two historical-prose references noted above remain.Privacy
Documentation and packaging only — no code paths, storage behavior, or data handling changed.
🤖 Generated with Claude Code
https://claude.ai/code/session_015LY7xtercMc3NtLeX2z4YV