v1.38.9 — date order everywhere, plain-HTTP writes, gateway errors named - #926
Merged
Conversation
…ateway errors named
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.
Three fixes that landed on main today, each from a report.
The date order you choose reaches every date on screen (#922). The preference reached the entry form and nothing else, because the formatter took it as an optional argument with a default. The default is gone, every caller carries the preference, and a guard refuses a numeric date renderer that does not.
A plain-HTTP self-host can write again (discussion #492). Not just uploads: every write minted its idempotency key with
crypto.randomUUID(), which the browser withholds from a non-HTTPS page, so on a LAN self-host nothing was saved and nothing said why. A random id that is not gated replaces it, with a guard.A gateway that refuses now says why. OpenRouter returns HTTP 200 with an embedded error on a provider failure; HealthLog reported it as "empty content", status 0. The embedded code and message now surface on the provider health card and in the ledger, for the OpenAI-compatible gateway and the local provider alike.
Each change had its own green run and its own mutation proof before merging; this branch only bumps the version and heads the changelog.