web: record v0.9.12 as the published release - #5886
Conversation
sync-latest-release wrote v0.9.12 (2026-09-05T09:59:53Z) to both facts files; derive-facts regenerated. Trust, FAQ, roadmap, and the facts telemetry line now say the earlier 0.9.11 release asked first, since 0.9.12 is the published release. Website vitest 407 passed; locales, facts OK. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Bs5x11yXAg3sJ4giZf4krF
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Claude finished @Hmbown's task in 1m 15s —— View job Reviewing PR #5886
SummaryThis is a clean, well-scoped post-release facts sync. No source/logic changes — only data and copy. Verified:
Not verified (no network/dependency access in this review environment): couldn't run No correctness, provider/model-routing, or security concerns — out of scope for this PR anyway (pure content/data sync). |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_5eef1448-750e-4241-8558-68f3127920be) |
There was a problem hiding this comment.
🟡 Changes recommended
docs/public-surface-facts.json still references “released v0.9.11 providers” in providerCountDefinition, which now reads inconsistent with the PR’s v0.9.12 “latest published release” update.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Updates the website “published release” facts and related trust/telemetry copy to reflect v0.9.12 as the latest published release, keeping the deploy-time public-surface facts/contract comparison consistent with GitHub.
Changes:
- Bump
latestPublishedReleasefrom v0.9.11 → v0.9.12 across website data and derived facts outputs. - Update trust/telemetry wording to refer to “the earlier 0.9.11 release” (rather than “the published 0.9.11 release”) across FAQ/roadmap/i18n/catalog and the public-surface facts contract test.
- Regenerate
web/lib/facts.generated.tswith updated timestamps and release metadata.
File summaries
| File | Description |
|---|---|
| web/lib/public-surface-contract.test.ts | Updates contract assertion to match the new “earlier 0.9.11” telemetry phrasing. |
| web/lib/i18n/dictionaries/zh/docs-trust.ts | Adjusts ZH trust/telemetry lead wording to “earlier 0.9.11”. |
| web/lib/i18n/dictionaries/en/docs-trust.ts | Adjusts EN trust/telemetry lead wording to “earlier 0.9.11”. |
| web/lib/facts.generated.ts | Regenerated facts: new generatedAt + latestPublishedRelease v0.9.12. |
| web/gt-catalog/zh.json | Updates ZH catalog telemetry lead wording. |
| web/gt-catalog/en.json | Updates EN catalog telemetry lead wording. |
| web/data/latest-published-release.json | Records v0.9.12 as latest published release (tag/version/date/url). |
| web/app/[locale]/roadmap/page.tsx | Updates roadmap telemetry paragraph to “earlier 0.9.11”. |
| web/app/[locale]/faq/page.tsx | Updates FAQ telemetry sentence to “earlier 0.9.11”. |
| docs/public-surface-facts.json | Syncs latestPublishedRelease to v0.9.12 and updates telemetry wording in trust facts. |
Review details
- Files reviewed: 10/10 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| @@ -36,10 +36,10 @@ | |||
| "providerCountDefinition": "Website-derived ApiProvider labels in this source snapshot, excluding Custom, DeepseekCN and retired Antigravity; includes protocol/plan variants. Not a count of distinct vendors, ProviderKind identities, live catalogs, or released v0.9.11 providers." | |||
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 89ddd755b8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "tag": "v0.9.12", | ||
| "version": "0.9.12", |
There was a problem hiding this comment.
When this marker advances the published release to v0.9.12, sourceCandidate.providerCountDefinition immediately above still distinguishes the source-derived count only from “released v0.9.11 providers.” The canonical facts therefore no longer clarify whether 46 represents the current published release’s provider surface; update that qualifier to v0.9.12 or, preferably, the release-neutral “released provider count” wording already used by the claim audit.
AGENTS.md reference: AGENTS.md:L3-L5
Useful? React with 👍 / 👎.
| The Codewhale runtime, workspace state, and audit log stay on your machine. | ||
| Codewhale 0.9.12 counts anonymous usage by default and says so at first launch | ||
| (the published 0.9.11 release asked first). Turning it off is a saved choice that | ||
| (the earlier 0.9.11 release asked first). Turning it off is a saved choice that |
There was a problem hiding this comment.
For this release wording change, the English and Chinese sentence is edited directly in both faq/page.tsx and roadmap/page.tsx even though the canonical docs-trust copy is separately maintained in dictionaries and GT catalogs. That preserves multiple independently editable translations, so the next release or privacy correction can pass locale checks while these public pages disagree; move the shared claim into lib/content or locale dictionaries and consume it from both pages.
AGENTS.md reference: web/AGENTS.md:L9-L15
Useful? React with 👍 / 👎.
![codewhale-agent[bot]](https://avatars.githubusercontent.com/u/101357273?s=60&v=4){kind=small}
There was a problem hiding this comment.
Codewhale review
PR updates latest published release facts to v0.9.12 and rewrites telemetry/trust wording from “the published 0.9.11 release asked first” to “the earlier 0.9.11 release asked first” across docs, FAQ, roadmap, GT catalog, and dictionaries. Generated facts and the public-surface contract test are also updated.
Findings
- [WARNING] Stale v0.9.11 reference remains in providerCountDefinition (
docs/public-surface-facts.json:36)
docs/public-surface-facts.json still says the provider count is not a count of "released v0.9.11 providers" even though the PR changes latestPublishedRelease to v0.9.12. If the definition is meant to reference the latest release, this is now stale and can make the public-surface facts inconsistent.
Assessment
Release fact sync is mostly consistent and low risk, but the stale v0.9.11 reference in providerCountDefinition should be checked or updated before deploy.
Advisory review by Codewhale (codewhale review --pr 5886 --post, head 89ddd755b8b2ae2e14b95564c2253c1b9332c4e3). Line-specific findings are also posted as inline review comments; mechanical fixes arrive as committable suggestions you can apply from the Files tab. CODEOWNERS approval still governs merge.
| @@ -36,10 +36,10 @@ | |||
| "providerCountDefinition": "Website-derived ApiProvider labels in this source snapshot, excluding Custom, DeepseekCN and retired Antigravity; includes protocol/plan variants. Not a count of distinct vendors, ProviderKind identities, live catalogs, or released v0.9.11 providers." | |||
There was a problem hiding this comment.
[WARNING] Stale v0.9.11 reference remains in providerCountDefinition
docs/public-surface-facts.json still says the provider count is not a count of "released v0.9.11 providers" even though the PR changes latestPublishedRelease to v0.9.12. If the definition is meant to reference the latest release, this is now stale and can make the public-surface facts inconsistent.
Post-release facts sync: latestPublishedRelease -> v0.9.12; trust/FAQ/roadmap wording moves from "the published 0.9.11 release asked first" to "the earlier 0.9.11 release asked first". Website vitest 407 passed; locales and facts checks OK. Needed before the web deploy so the post-deploy facts comparison passes.
No-Issue: release follow-up.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Bs5x11yXAg3sJ4giZf4krF
Note
Low Risk
Documentation and generated facts only; no runtime, auth, or API behavior changes.
Overview
Post-release facts sync so the site and public-surface contract match GitHub after v0.9.12 shipped.
latestPublishedReleasemoves from 0.9.11 to 0.9.12 (tag,publishedAt, release URL) inweb/data/latest-published-release.json,docs/public-surface-facts.json, and regeneratedweb/lib/facts.generated.ts.Trust/telemetry copy no longer calls 0.9.11 “the published … release”; it now says the earlier 0.9.11 release asked first for opt-in, since 0.9.12 is the current published release. That wording is aligned across FAQ, roadmap, GT catalog, docs-trust dictionaries (EN/ZH), and the trust block in public-surface facts.
public-surface-contract.test.tsasserts the new telemetry phrase (earlier 0.9.11 release asked first) so deploy-time facts checks stay green.Reviewed by Cursor Bugbot for commit 89ddd75. Bugbot is set up for automated code reviews on this repo. Configure here.