Skip to content

release: v0.5.0 - #123

Merged
AutumnsGrove merged 2 commits into
mainfrom
release/v0.5.0
Nov 14, 2026
Merged

AutumnsGrove merged 2 commits into
mainfrom
release/v0.5.0

Conversation

@AutumnsGrove

Copy link
Copy Markdown
Owner

release: v0.5.0

Renames [Unreleased] to [0.5.0] - 2026-11-14, leaves a fresh empty [Unreleased], and moves the compare link to v0.5.0...HEAD.

Minor, not a patch (as we discussed): the section removes four exported symbols and adds a public package, which AGENTS.md puts in the minor column for v0.x. Upgrade notes at the top of the section, in the order a consumer hits them:

  • voice/openrouter.Config.CostTimeout and DefaultCostTimeout removed — speech cost is a catalog estimate now, so there is no lookup to bound.
  • voice/openrouter.DefaultSpeechModel and DefaultTranscribeModel removed — a model always came from a role.
  • The minimum Go is 1.26.11, up from 1.26.6 (GO-2026-6859 in net/http, reachable through nova serve, provider/ssestream and auth).
  • Additive and no edit needed: the endpoint fields on voice.VoiceRole/VoiceAttempt/TranscribeRole/RolesConfig, and the new voice/openai.

I read every entry in the section rather than assuming: the two voice/openrouter removals and the Go floor are the only caller-visible breakages, and the rest is additive — the endpoint config, the release-gate work, the security/fuzz/nightly workflows, the provider pin, session naming, the resume hint, the two fuzz findings (#107, #108), the voice doc correction, and #57.

make ci green locally on this branch.

On merge: tag the merge commit v0.5.0 on main and push it, which starts the release workflow (acceptance for every chunk, four binaries, a release page). I will watch it and check the module resolves.

A minor rather than the patch the section's size would suggest: it removes four
exported symbols — `voice/openrouter.Config.CostTimeout`, `DefaultCostTimeout`,
`DefaultSpeechModel` and `DefaultTranscribeModel` — and adds a public package, so
`v0.x` calls it a minor. The upgrade notes name each one.

@pi-review-autumnsgrove pi-review-autumnsgrove Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Release-only changelog PR. I verified the mechanical parts against v0.4.1..HEAD:

  • [Unreleased] is renamed with today's UTC date (2026-11-14) and a new empty section sits above it.
  • The four named symbols (Config.CostTimeout, DefaultCostTimeout, DefaultSpeechModel, DefaultTranscribeModel) really existed at v0.4.1 and are gone at HEAD; a scan of the range found no other removed exported function, method, type, or constant.
  • go.mod was go 1.26.6 at v0.4.1 and is go 1.26.11 at HEAD, matching the notes.
  • The endpoint/map additions to voice.VoiceRole, VoiceAttempt, TranscribeRole, and RolesConfig are additive and the zero values route exactly as before.
  • The [0.5.0] link and the moved [Unreleased] compare link are correct, and scripts/release-notes extracts the new section (its tests pass).

One accuracy gap in the upgrade notes: callers who set voice/openrouter.Config.CostLookup do see different output, which is not listed. Otherwise the section is a faithful rename of [Unreleased] and there is nothing else significant to flag.

Comment thread CHANGELOG.md

- `voice/openrouter.Config.CostTimeout` and `voice/openrouter.DefaultCostTimeout` are removed. Speech
cost is now an estimate from the catalog, so there is no separate lookup to bound. Drop the field
and the constant; nothing else changes.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This says dropping CostTimeout changes nothing else, but callers who use Config.CostLookup get different results. In v0.4.1 the /generation lookup returned an all-null record for gen-tts-*, so Usage.CostUSD stayed 0 and CostSource was never set; at HEAD the same configuration returns runes * pricePerMillion / 1e6 with CostSource: "catalog". The ### Changed entry records the new estimate, but the upgrade notes (the part a consumer reads first, and what the PR summary calls the only caller-visible changes) omit it. Since cost_lookup defaults on for the front doors, this is visible from nova speak too. Add a bullet naming the new cost/CostSource values alongside the removed field.

@pi-review-autumnsgrove

pi-review-autumnsgrove Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

pi-review reviewed c307bc9e02f4 — commented · 0 inline comments · details

@pi-review-autumnsgrove pi-review-autumnsgrove Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The only change since the previous review is four lines of upgrade notes in CHANGELOG.md for [0.5.0], closing the gap I raised about voice/openrouter.Config.CostLookup.

I checked the added text against the code and docs/DECISIONS.md D171:

  • CostLookup is still only a switch that fills Clip.Usage; the value is now runes * pricePerMillion / 1e6 with CostSource: "catalog" (voice/openrouter/speak.go, cost.go), not the retired /generation lookup.
  • The /generation semantics in the note ("answered all nulls") match docs/VOICE.md and test TestSpeak_A10_CostIsEstimatedFromTheCatalog.
  • Pin-endpoint pricing matches pricePerMillion/pinnedProvider: a pin naming exactly one provider is read from the endpoint table, so the figure moves by the endpoint price ratio (A38), while a multi-name/order pin falls back to the roster rate.
  • go test ./scripts/release-notes/... still passes, so the section still extracts cleanly.

The release notes are now accurate for all four caller-visible items (the two removals, the Go floor, and CostLookup), plus the additive list. Nothing significant remains to flag.

@AutumnsGrove
AutumnsGrove merged commit f5a3b0d into main Nov 14, 2026
5 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