Bump every version reference to 1.0 and polish the docs site (v1.0 release prep) - #71
Merged
Conversation
Release prep for v1.0 (not the tag itself): - version.mk -> 1.0, host/pyproject.toml -> 1.0.0 - amipilot.readme: Version 1.0 plus a "From 1.0" features paragraph (FSPUT, WBLAUNCH, SCREENSHOT incl. P96, WINDOWMOVE/WINDOWSIZE, WAITFOR REQUESTER) - userdocs/Changelog.md: full v1.0 entry with known gaps - userdocs/Wire-Protocol.md: the example VERSION handshake was stale twice over -- it said 0.5 AND its EXPERIMENTAL verb list was missing WINDOWMOVE/WINDOWSIZE (the server's real list has them); byte count recomputed to match the corrected payload - userdocs/Installation.md: version example -> 1.0 - README.md, host/README.md, CLAUDE.md: status text updated from "phase 1.0 in progress" to released; host/README also gains the missing 1.0 items (amipilot.screenshot module, wb_launch/fs_put/ window_move/window_resize/screenshot in the client verb list) Verified: mkdocs build --strict clean (also caught and fixed one bad anchor in the new changelog entry), host pytest suite 235 passed. Deliberately NOT done here: the WIRE.md "1.0 promotion pass" (moving verbs from EXPERIMENTAL to STABLE in the handshake) -- that is a compatibility promise, left as an explicit pre-tag decision. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Tge64MCjRcKLXiFcszvxwb
This was referenced Aug 9, 2026
sidick
added a commit
that referenced
this pull request
Aug 10, 2026
Release prep for the imminent v1.1 tag. ## Version bumps - version.mk -> 1.1, host/pyproject.toml -> 1.1.0 - amipilot.readme: Version field -> 1.1 plus a new "From 1.1" features paragraph (PICK, full Requester close, pointer-based MENUPICK, WHERE/WHEREGADGET, STRING_KIND/INTEGER_KIND, 12 more ReAction roles) - README.md, host/README.md, CLAUDE.md, server/README.md: status text flipped from "not yet in a tagged release"/"not yet released" to shipped-in-v1.1, matching the v1.0 release-prep precedent (PR #71) ## Docs pass - userdocs/Changelog.md: renamed "## Unreleased" to "## v1.1", and added the three entries that PRs #83/#84/#85 (PyPI, on_progress, PICK) never wrote there in the first place -- the five requester/ ReAction/WHERE/MENUPICK/STRING-INTEGER entries were already present - userdocs/ARexx-Reference.md: PICK was entirely missing from the verb table -- added - userdocs/Use-Cases.md, Getting-Started.md: point at PICK from the "exploratory GUI inspection" use case and the getting-started walkthrough, where it now genuinely delivers on the long-standing "element-picker equivalent" claim - userdocs/Troubleshooting-and-FAQ.md: new PICK entry covering the three real gotchas (single-snapshot semantics, system gadgets in an "empty" chrome hit, the untested-display-modes caveat on the pointer-Y correction) - userdocs/Wire-Protocol.md: the one live "pip install amipilot[serial]" instruction now hedges on PyPI publishing not being live yet, matching skills/amipilot/SKILL.md's own existing hedge ## Verified - scripts/verify-version.sh v1.1 passes (version.mk/amipilot.readme/ host/pyproject.toml all agree) - amipilot.readme: no line exceeds Aminet's 72-char limit - mkdocs build --strict clean (also confirms the new #pick-mode-pick anchor resolves) - make guide (AmigaGuide conversion) succeeds - Host unit suite: 246 passed ## Deliberately NOT in this PR -- open pre-tag decisions 1. PyPI's one-time setup (pending publisher + `pypi` environment) is still outstanding -- confirmed neither exists yet. Pushing the tag now would leave the publish-pypi job failing on a missing environment. Needs doing (or the job needs skipping for this tag) before/at tag time. 2. The GitHub repo description update (standing release checklist item) -- a live setting change, not a file in this PR. 3. The tag itself and the GitHub release/Aminet pipeline it triggers.
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.
Release prep for the imminent v1.0 tag — every version reference updated to 1.0, plus a polish pass over the docs site.
Version bumps
version.mk→ 1.0,host/pyproject.toml→ 1.0.0amipilot.readme: Version field → 1.0 plus a new "From 1.0" features paragraph (FSPUT, WBLAUNCH, SCREENSHOT incl. Picasso96/RTG, WINDOWMOVE/WINDOWSIZE, WAITFOR REQUESTER) — folded into this same PR rather than the historical second-PR pattern, so it can't ship staleREADME.md,host/README.md,CLAUDE.md: status text updated from "phase 1.0 in progress, not yet tagged" to releasedDocs site polish
userdocs/Changelog.md: full v1.0 entry ("what's in 1.0" + known gaps, matching the entry style of prior releases) — content ready to reuse for the GitHub release notesuserdocs/Wire-Protocol.md: the exampleVERSIONhandshake was stale twice over — it saidAMIPILOT 0.5AND itsEXPERIMENTALverb list was missingWINDOWMOVE WINDOWSIZE(the server's real handshake inamipilotserver/main.cincludes them); byte count in the example recomputed (208 → 230) to match the corrected payloaduserdocs/Installation.md: version example → 1.0host/README.md: gains the 1.0 items it was missing — anamipilot.screenshotmodule bullet, andwb_launch()/fs_put()/window_move()/window_resize()/screenshot()in the client verb listVerified
mkdocs build --strictclean (it caught one bad anchor in the new changelog entry, fixed)Deliberately NOT in this PR — open pre-tag decisions
WIRE.md"1.0 promotion pass": the handshake still lists every verb asEXPERIMENTAL, and WIRE.md says that holds "until the 1.0 promotion pass". Promoting verbs toSTABLEis a never-break-within-a-major compatibility promise, so it's left as an explicit decision, not made silently here.🤖 Generated with Claude Code
https://claude.ai/code/session_01Tge64MCjRcKLXiFcszvxwb