Say what the last change actually did, in the changelog and the docs - #634
Merged
Merged
Conversation
The Unreleased entry described a desktop release for a commit that also put a new route on the server. Rewritten against the code rather than the summary. What it was getting wrong: Bun is not "replaced", the version already on the machine is left untouched and simply not used, and the check now gates Start as well as install. Repair moved under Installation options on the install screen only; it is still a top-level button on the stopped screen. "Existing Docker credentials are preserved" described code that is not in the tree, since nothing reads or writes Docker's config.json; the real change is that the inherited PATH is now kept and appended to rather than replaced. What it was missing: OPENBOT_MODEL_OAUTH_FILE and the route it mounts, the Gemini transport, a provider 403 no longer reading as an expired sign-in, the leftover-database reset, the Windows Compose separator, and the organization sign-in fix for a callback that arrives in pieces. The docs had drifted in the two files that call themselves the full reference. charts/openbot/README.md never absorbed computers.podSecurityContext, so an existing k3s install upgrading to 0.0.14 hits CrashLoopBackOff with the explanation only in the changelog; that upgrade note is the one operators will actually need. docs/configuration.md was missing SIGNIN_ALLOWED_EMAIL_DOMAINS, OPENBOT_ORGANIZATION_AUTH_URL and OPENBOT_ACCESSIBILITY_DISABLED, and said nothing about the desktop owning OPENAI_BASE_URL and OPENAI_API_KEY under provider OAuth. docs/architecture.md now lists the new route beside the other boundaries, and the docs index links the two desktop documents nothing pointed at.
davidmckayv
requested review from
MikeRyanDev,
guidovizoso,
mxmzb and
tylerslaton
as code owners
September 22, 2026 03:33
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
1 participant
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.
Validated the
Unreleasedchangelog section claim by claim against the tree, then swept the docs for drift. Code was the only source of truth.Changelog was inaccurate in three places
install.rs:1002-1018), and the check now gates Start too (preparation.rs:231-232).App.tsx:762-769), not on the stopped screen where it is still top-level (App.tsx:890-898).config.json. The real change is thatAddress::command()now keeps the inherited PATH instead of replacing it (engine.rs:337-339).Changelog was incomplete. The entry told a desktop-only story for a commit that also lands on the released server:
OPENBOT_MODEL_OAUTH_FILEand thePOST /api/model-provider/v1/chat/completionsit mounts (provider-oauth.ts:341,index.ts:1313-1315)google-oauth-transport.ts)desktop-connection-failure.ts)stack.rs:320-355)stack.rs:508-513)organization_auth.rs)Docs
charts/openbot/README.mdhad zero mentions ofpodSecurityContext,fsGroup,hostPathorlocal-pathdespite 0.0.14 moving computers to uid 1001. An existing k3s install upgrading hits CrashLoopBackOff, becausefsGroupis not applied by hostPath-backed provisioners, and the chart docs said nothing. Adds that upgrade note, including the--reuse-valuestrap.docs/configuration.md: addsSIGNIN_ALLOWED_EMAIL_DOMAINS,OPENBOT_ORGANIZATION_AUTH_URL(with its HTTPS and bare-origin rules) andOPENBOT_ACCESSIBILITY_DISABLED, plus a note that the desktop ownsOPENAI_BASE_URL/OPENAI_API_KEYunder provider OAuth.docs/architecture.md: the new route beside the other security boundaries.docs/README.md: linksPROVIDER_OAUTH.mdandTELEMETRY.md, which nothing pointed at.desktop/PROVIDER_OAUTH.md: namesVITE_OPENBOT_SUPPORT_URL.Released changelog sections are byte-identical to main. Docs and changelog only, no code.