Docs for Lite 2026.10.6, core 0.63.0 and ThinkWatch 3.2.0 - #64
Merged
Merged
Conversation
…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>
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
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.
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):failover-and-load-balancing.md:keep-api-keys-from-relays.md: points at the marks on the upstream's row instead of the removed Check-up tab.ThinkWatch
deployment-guide.mdadds section 4.6, External PostgreSQL and Redis, following the chart README:redis-cluster://.rediss:///rediss-cluster://, withREDIS_CA_CERT/redis.caSecretfor a private CA.secrets.databaseUrl/secrets.redisUrl, which the chart does not have.configuration.md:DATABASE_URLandREDIS_URLlink to the new section.JWT_SECRETandENCRYPTION_KEYinto 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 leavesecrets.jwtSecret/secrets.encryptionKeyunset, to restart the server after the first sync, and that the database URLs come fromexternalUrl.Not in this PR
src/data/core-docs). It is refreshed withCORE_DOCS_REF=v0.63.0 pnpm core-docsonce v0.63.0 is tagged.pnpm buildpasses.🤖 Generated with Claude Code