Skip to content

Docs for Lite 2026.10.6, core 0.63.0 and ThinkWatch 3.2.0 - #64

Merged
fylorn merged 4 commits into
mainfrom
docs/release-2026-10-6
Oct 5, 2026
Merged

fylorn merged 4 commits into
mainfrom
docs/release-2026-10-6

Conversation

@fylorn

@fylorn fylorn commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

Site docs for the joint release: ThinkWatch Lite 2026.10.6 (core 0.63.0, ThinkWatch-Core#292, ThinkWatch-Lite#285, #286) and ThinkWatch 3.2.0 (ThinkWatch#81–#83).

Lite

  • features.md (en, zh-CN):
    • Round-robin groups: a weight per member and Distribute by (ratio, speed, reliability, or both).
    • Move to the next upstream when the start times out, and the slot wait in Settings › Failover.
    • A concurrency limit per upstream, and model specs set by hand (Specs…).
    • Key usage limits, with the Limit reached mark and the notifications at 80% and at the limit.
    • New marks in a request's attempts: a start that timed out with possibly billed input, skips at the concurrency limit, and time queued. Requests refused by a usage limit or because every upstream was full are labelled.
    • Responses WebSocket turns are listed as requests.
    • Check-up findings now appear on the upstream's row; the paragraph about the removed tab is gone.
  • failover-and-load-balancing.md:
    • The strategy table now says weights decide the round-robin split, and that Lowest latency is measured as time to first token per attempt.
    • New notes on weights and the distribution factors, slow starts and concurrency limits.
    • The guide now follows 2026.10.6.
  • keep-api-keys-from-relays.md: points at the marks on the upstream's row instead of the removed Check-up tab.
  • Lite page: the keys tile mentions usage limits.

ThinkWatch

  • deployment-guide.md adds section 4.6, External PostgreSQL and Redis, following the chart README:
    • Postgres must be reached directly or through a session-mode pooler, not a transaction-mode one, because schema setup holds a session advisory lock.
    • Redis Cluster uses redis-cluster://.
    • Redis over TLS uses rediss:// / rediss-cluster://, with REDIS_CA_CERT / redis.caSecret for a private CA.
  • The Helm install example no longer sets secrets.databaseUrl / secrets.redisUrl, which the chart does not have.
  • configuration.md: DATABASE_URL and REDIS_URL link to the new section.
  • Section 4.4, External Secrets: the ExternalSecret example now merges JWT_SECRET and ENCRYPTION_KEY into the chart's own <release>-secrets (creationPolicy: Merge, external-secrets.io/v1). Before, it used lower-case keys the server never reads and a Secret the chart overwrites. The text says to leave secrets.jwtSecret / secrets.encryptionKey unset, to restart the server after the first sync, and that the database URLs come from externalUrl.

Not in this PR

  • The core docs snapshot (src/data/core-docs). It is refreshed with CORE_DOCS_REF=v0.63.0 pnpm core-docs once v0.63.0 is tagged.

pnpm build passes.

🤖 Generated with Claude Code

fylorn and others added 4 commits October 5, 2026 21:43
…cy, model specs, key usage limits

Lite 2026.10.6 (core 0.63.0) changes how groups distribute requests and
adds limits that the features page and the failover guide did not
describe, and it drops the Check-up tab that two pages still sent
readers to.

- Features: weights and "Distribute by" on round-robin groups; moving a
  slow-starting stream to the next upstream; the concurrency limit per
  upstream and the slot wait in Settings › Failover; model specs set by
  hand; usage limits per key with the "Limit reached" mark and
  notifications; the new marks in a request's attempts; Responses
  WebSocket turns as requests; check-up findings on the upstream's row.
- Failover guide: weights and the four distribution modes with their
  factors, slow starts, concurrency limits, and "Lowest latency" now
  measured as time to first token per attempt.
- Relay guide: points at the marks on the upstream's row instead of the
  removed tab.
- Lite page: the keys tile mentions usage limits.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…d Redis over TLS

ThinkWatch 3.2.0 takes a session-level advisory lock while it sets up
the schema, so a transaction-mode pooler can leave the lock held and
stall every later start; it also connects to Redis over TLS
(rediss://, rediss-cluster://, REDIS_CA_CERT for a private CA) and to a
Redis Cluster. The guide said nothing about either, and its Helm example
set secrets.databaseUrl and secrets.redisUrl, which the chart does not
have.

- New section 4.6 with the chart's bundled: false / externalUrl values,
  the pooler requirement, the Cluster URL form and the TLS settings,
  following the chart README.
- The Helm install example drops the two values the chart ignores and
  says that it runs the databases itself unless told otherwise.
- The configuration reference points DATABASE_URL and REDIS_URL at the
  new section.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…chart

The 4.4 example wrote lower-case keys (jwt-secret, database-url, ...)
that the server never reads, created a Secret the chart also creates
and overwrites, and used the v1beta1 API that current External Secrets
Operator releases no longer serve.

The chart always renders <release>-secrets and the server reads it
through envFrom, with upper-case variable names. The example now merges
JWT_SECRET and ENCRYPTION_KEY into that Secret (creationPolicy: Merge,
external-secrets.io/v1), which the chart reads back on upgrade. The
text says to leave secrets.jwtSecret and secrets.encryptionKey unset,
to restart the server after the first sync, and that DATABASE_URL and
REDIS_URL come from postgres.externalUrl and redis.externalUrl, since
the chart rewrites them on every upgrade.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…y, model specs and key usage limits

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@fylorn
fylorn marked this pull request as ready for review October 5, 2026 14:43
@fylorn
fylorn merged commit 1fc21e0 into main Oct 5, 2026
1 check passed
@fylorn
fylorn deleted the docs/release-2026-10-6 branch October 5, 2026 14:43
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