graff — a fast agentic coding harness in Zig: multi-provider, MCP, workflows, DGM evolution loop, TS/Python SDKs
Python
Prepare v0.302.64 release
justrach5f2216384cac
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 9b8a9d2d..ccc71bda 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -10,6 +10,11 @@ The release workflow uses a tag's section here as its release notes (ahand-written `docs/releases/<tag>.md` wins if present), so keeping this filecurrent is part of cutting a release.+## v0.302.64++- An expired Anthropic Console sign-in that can't be renewed is skipped instead of sent. With no refresh token stored, `ant auth print-credentials` exits 0 and prints the same expired token; graff took that as a refresh, so the dead token was used (or kept as the fallback behind a Claude plan) and every request came back 401. Errors now say "Anthropic Console sign-in has expired: run `graff login console` again", including after a plan handoff, and a spent plan whose fallback was skipped says why (#1781, ADR 0310).+- Retains all changes from v0.302.63.+## v0.302.63- An authentication failure names the credential that was rejected. A sign-in says "<Provider> sign-in was rejected: sign in again (<login command>)"; an API key says "<Provider> API key was rejected (<source>): replace or remove the key. Your sign-in is not affected."; and a key graff fell back to after a plan ran out says "<Provider> plan is out of usage, and the fallback API key was rejected (<source>)". Before, every case read "provider authentication failed: sign in again or check the API key", so a client showed "Log in" when the key was the problem (#1779, ADR 0310).diff --git a/docs/releases/v0.302.64.md b/docs/releases/v0.302.64.mdnew file mode 100644index 00000000..1148ab86--- /dev/null+++ b/docs/releases/v0.302.64.md@@ -0,0 +1,8 @@+# v0.302.64++An expired Anthropic Console sign-in is skipped, and the error says so.++- **No more dead Console token.** When a Console sign-in's token has expired and no refresh token is stored, `ant auth print-credentials --access-token` warns but exits 0 and prints the same expired token. graff took that as a successful refresh, so it kept using the token, or kept it as the fallback behind a Claude plan, and every request came back 401. A renewal that returns the old token now counts as failed: the expired sign-in is neither used nor kept as a fallback, and mid-session graff stops sending it.+- **The error names it.** "Anthropic Console sign-in has expired: run `graff login console` again. Your sign-in is not affected." After a plan handoff it says the fallback Console sign-in has expired, and when a plan runs out with no fallback for that reason: "Anthropic plan is out of quota, and the Console sign-in that would take over has expired: run `graff login console` again, or wait for the plan to reset." (#1781, ADR 0310)++Includes all changes from v0.302.63.diff --git a/scripts/eval/tier1-manifest.json b/scripts/eval/tier1-manifest.jsonindex c28c6dd1..91961727 100644--- a/scripts/eval/tier1-manifest.json+++ b/scripts/eval/tier1-manifest.json@@ -14,7 +14,7 @@"src/main.zig","src/repl.zig"],- "test_count_baseline": 3579,+ "test_count_baseline": 3580,"test_count_slack": 25,"required_invariants": [{diff --git a/src/cli_text_source.zig b/src/cli_text_source.zigindex 3623f6db..3ef656e3 100644--- a/src/cli_text_source.zig+++ b/src/cli_text_source.zig@@ -5,6 +5,9 @@pub const changelog_text =\\What's new\\──────────+ \\0.302.64+ \\ • an expired Console sign-in is skipped, and the error says to run graff login console+ \\\\0.302.63\\ • auth errors say which credential was rejected: the sign-in, or the API key (and when it was the fallback)\\