- refactor: Move Ask User Question Cards Into the Chat Package
- fix: Preserve Ask Card Styling Without Suppression Growth
- fix: Provide Live Ask Pauses As Scoped Context Data
- test: Cover the Settled Ask Record Collapse Cascade
- fix: Give the Ask Call Spec Host the Tool Call Chrome
- refactor: Move the Composer Palette Into the Chat Package
- fix: Keep the Palette Usable Without a Windowed List or Catalog Host
- test: Cover Picking Palette Rows With the Mouse
- fix: Leave Palette Keys to IME Composition and Focus to the Field a Press Moved It To
- fix: Localize the Palette Without Its Data Host
- fix: Ship the Composer Popover Motion With the Client Package
- test: Check the Composer Motion Survives the App Cascade
- fix: Offer Palette Favorites Only Where the Host Stores Them
- fix: Name the Palette Favorite Shortcut Only Where It Works
- fix: Leave the Bookmark Shortcut Alone Where the Palette Stores No Favorites
- refactor: Render Pending Turn and Steers from the Package
- refactor: Keep Package Pending Rows Inert Without a Steer Host
- fix: Read the Host Thread Mode on Every Render
- fix: Point the Hosts Guard at the Messages Loader
- fix: Follow the Moved Pending Rows in the Guard and Lazy Chunk Specs
- fix: Ship Message Body Typography With the Shared Theme Styles
- fix: Keep the App Message Typography Cascade With the Shared Styles
* ci: Record Playwright Shard Timings From Green Dev Runs
* ci: Run the Playwright Mock Suite on Fifteen Memory Shards
* ci: Run the Playwright Workflow Script Tests Once per Run
* test: Make the Due Schedule E2E Wait for One Engine Tick Only
* test: Cover the Shard Timings Hand-off With Acceptance Scenarios
* perf: Paint the Loading Shell Before the Bundle Arrives
* fix: Name a Lost Connection Instead of Suggesting a Refresh
* fix: Give the Endpoint Key Button a Usable Touch Target
* test: Cover the Loading Shell, Offline Copy and Key Button Target
* fix: Announce the Loading Indicator in the User's Language
* test: Exercise the Key Button on a Plain Endpoint Row and the Localized Label
* test: Measure the Key Button's Layout Size, Not Its Animated Box
* fix: Keep the Key Button's Row Height on Fine Pointers Too
* fix: Ink the Loading Indicator in the Theme's Text Role
* fix: Draw the Loading Indicator With the Shared Spinner
* test: List the Loading Spinner Spec as an index.html Guard
* fix: Resolve the Loading Label's Language the Way the App Does
* test: Cover the Loading Label for an Automatic zh-TW Browser
* feat: Add Choice Cards, Raised Radio Tone and Section Add Button
* fix: Size the Section Add Button From a Theme Role and Cover the Shared Controls in E2E
* test: Cover the New Shared Controls Under a Reference Theme
* test: List the Shared Controls Theme Spec in the Guard Manifest
On 2026-11-11 the artifact service answered every request with an HTML
page. In Playwright run 43092661470 eight memory shards failed in
"Upload Playwright HTML report" after retrying for 9 to 10.5 minutes;
in six of them every test had passed.
Uploads that no job downloads (Playwright reports, traces and
screenshots, the Lighthouse report, the advisory quality reports) are
now `continue-on-error` with a three minute step timeout, so a failed
upload stays out of the job result and a stalled one cannot run the job
into its own timeout. The Jest result uploads were already
`continue-on-error` and gain the same bound. Build outputs and mutation
shards that a later job downloads stay fatal.
merge-gate.test.mjs holds the gated workflows to that split, and
workflow.test.mts holds Change Quality to it.
* 🦠 chore: Upgrade Node.js and Undici to Security Releases
* test: Wait for Restored Composer Readiness and Reuse Wrapping Config
---------
Co-authored-by: Lia <lia@librechat.ai>
* 🚦 ci: Make Dev Workflows Ready for a Merge Queue
* ♻️ ci: Evaluate Merge Gate Expressions With the Shared Workflow Evaluator
* 🧺 ci: Share the Installed Tree in Merge Gate Tests the Way ci-setup Requires
* 🍃 ci: Provision the mongod Binary Before Tests Start
mongodb-memory-server downloads its ~122 MB mongod the first time a test
starts a server, inside a 15 s beforeAll. Only backend-review.yml cached
~/.cache/mongodb-binaries (the same step pasted four times), and a cache
alone still leaves the download inside the first hook on a miss.
Integration Tests downloaded on every run: 6 failures in 274 runs with
"Exceeded timeout of 15000 ms for a hook" in secrets.integration.spec.ts,
followed by "spawn ETXTBSY" in the suites that started mongod while the
timed-out download was still writing it.
Add .github/actions/mongodb-binary: restore the cache with the existing
key scheme, ask the installed mongodb-memory-server for the binary it
wants (MongoBinary.getPath), make sure that binary sits in the home cache
every working directory resolves, run it once, and save the cache right
away. The step fails the job when no runnable binary can be put in place.
Use it in every job that starts mongodb-memory-server, after dependencies
are installed and before tests, and add the action to the path filters of
the workflows that list their own file.
* 🧪 test: Cover the mongod Provisioning Script Without the Network
Run the real script against a stand-in resolver that keeps the properties it relies on: home cache first, download when missing, and a memoised path until the cache is cleared. Integration Tests runs the suite before it uses the action.
* 🧪 test: Run mongod Provisioning Against the Real Resolver
The suite replaced mongodb-memory-server with a hand-written stand-in, so
it checked the script against a description of the resolver rather than the
installed one. It now runs the script against the real library and
replaces only the network: MONGOMS_DOWNLOAD_MIRROR points at a local
server that serves an archive whose bin/mongod is a shell script, with the
.md5 the library verifies it against.
Recovery also no longer charges a broken copy that was already on disk to
the download: with a broken binary in both the home cache and the root
node_modules/.cache, the first attempt removed one, the retry met the
other, and the step failed without ever downloading. Existing copies are
now discarded one at a time and the download keeps its own two attempts.
* 🧪 test: Reach the Exit-Status Check Behind the Library's System Binary Probe
A system binary that prints nothing is rejected by the library's own version probe, so the case never reached this script's check or the rule that a file the job named is not deleted. Add one that answers the probe and exits non-zero.
Playwright reports a test that fails and then passes on a retry as "flaky" and exits 0, so a
regression that fails two attempts in three merges green. Set `failOnFlakyTests` in CI on the
mock profile (inherited by the Redis transport, registered-email and other derived profiles) and
on the base profile. Retry counts are unchanged: the later attempts still record the trace and
video and show whether a failure repeats.
A run failed this way still prints "N flaky" beside a passed count, so add a reporter that names
each retried pass in the job log and the job summary and says that it is what failed the run.
* 🥅 ci: Run Playwright After Every Merge to Dev
The mock e2e suite ran on pull requests, nightly on main and on demand, so
when a spec broke on dev no run on dev could go red: the vote workflow that
runs the suite after merges cannot fail by design.
Add a push trigger for dev with the pull request path filter. A push runs
the pull request profile with no lane narrowed (10 memory shards, 2 Redis
transport shards, both MCP lanes and MCP Apps), and the gate job reports it.
Pushes take their own concurrency group that never cancels: the run in
progress finishes, and GitHub keeps one pending run per group, so merges
that land meanwhile collapse into one run of the newest commit. Pull
request, nightly and manual runs keep their per-ref cancelling group.
The matrix test now evaluates the workflow's own expressions per event
rather than matching their text.
* 🔭 ci: Always Run Source-Scanning Guard Specs Under Test Selection
Codegraph test selection narrows a pull request run to the test files an
import graph reaches. A spec that reads source with fs has no import edge
to what it reads: toolCapabilityGates.spec.js scans four source trees, was
not selected when #17864 changed one of the files it counts, and failed on
dev afterwards.
List every such spec, with the paths it reads, in .github/guard-specs.json.
Both selectors now add a workspace's guards to a FILES decision and turn a
NONE into a guards-only run when the change touches a path one of them
reads, renames a file, or edits the list. A list that cannot be read runs
the workspace FULL. FULL decisions and every earlier fail-open path are
unchanged.
The rule keys off the decision, not the event. A selection with no file
left in the checkout gets no guards, so the test job still runs FULL on a
stale selection instead of running only the guards.
guard-specs.test.mjs fails when a spec in a gated workspace reads the
repository through fs without being listed, when a listed path is missing,
and when a workflow would not run for a path one of its guards reads. That
last check adds the five backend and one frontend paths the triggers
lacked. The test also runs both real select steps against canned codegraph
responses.
* 🧰 ci: Provision Pinned Redis Binaries Without a Distro Mirror
The MCP list_changed jobs and Cache Integration Tests installed redis-server and redis-tools with apt-get at test time. When the runners could not resolve the Ubuntu mirrors, apt-get update spent 3m20s giving up, the install stalled into the step timeout, and the next step found no redis-cli. The version was whatever the mirror served that day.
A composite action now restores redis-server and redis-cli 8.0.5 from the Actions cache and, on a miss, builds them once from the pinned upstream commit with bounded retries. The step fails with one clear error when Redis cannot be provisioned.
* 🔦 ci: Keep Lighthouse Running When the Ubuntu Mirror Is Unreachable
The Lighthouse job installed its pinned Chromium with `playwright install --with-deps`, which runs apt-get first. With the Ubuntu mirrors unresolvable, apt exited 100 and the job failed before any audit ran.
On the runner every library Chromium links is already present with the preinstalled Chrome; the only packages apt added were nine optional fonts. The browser download stays fatal and keeps the lockfile-pinned build, while the system packages go through the bounded best-effort script the Playwright jobs already use.
* ⏱️ ci: Give the Cold Redis Build Room on a Slow Runner
The first hosted runs built Redis in 49, 58 and 103 seconds. A 180 second cap left the slowest of those less than twice its own time, so a slower runner would have failed a job for being slow. The build may now take 300 seconds and the calling steps eight minutes; an unreachable host still fails within 98 seconds. The ready line reports the fetch and the build separately.
* ci: report mutation and change risk for edited functions
* ci: show function mutation progress in logs
* fix: Exclude Shared Database Test Suites from Quality Targets
---------
Co-authored-by: Lia <lia@librechat.ai>
* 🥐 chore: Standardize Bun-First Workspace Typechecks
* fix: Preserve Bun 1.4.3 Checker Compatibility
* chore: Pin Bun 1.4.4 for Local and CI Typechecks
---------
Co-authored-by: Lia <lia@librechat.ai>
Pushes to main that touch packages/data-provider/package.json without bumping the version failed with "You cannot publish over the previously published versions". Check whether the exact version already exists on the registry and skip packing and publishing when it does, as the client workflow does.
* ci: Add README Translation Sync Workflow
* ci: Pin create-pull-request Action in README Sync
* ci: Check Translation Content and Attribute Text in README Sync
* ci: Harden README Translation Validation and Switcher
* ci: Validate Protected Tokens in README Translations
* ci: Keep Link Order and Fence Boundaries in README Translation
* ci: Validate README Translations Against the Markdown Tree
* ci: Check Short Prose and Link Metadata in README Translation
* ci: Handle Brand Suffixes, Titles and Table Alignment in README Validation
* ci: Preserve Emoji, Image Alt and Raw Code in README Validation
* ci: Stop Rejecting Faithful Translations That Keep Language Names
* ci: Refresh Switchers in Unselected README Translations
* ci: Compare Comment Contents and Deduplicate Pending README Sections
* ci: Revalidate Cached README Translations and Resolve Reference Links
* ci: Keep Code in Raw HTML Blocks and Accept Full-Form Reference Translations
* ci: Read Alt Text of Reference-Style README Images
* ci: Test the README Translation Helpers on Pull Requests
* ci: Keep Reference Image Alt Text and Translate Definition Titles
* ci: Resolve README Reference Definitions Before Classifying Prose
* ci: Resolve README Footnotes When Validating Chunks
* ci: Point README Fragment Links at Translated Heading Anchors
Same-document links kept the English heading slug, which no longer exists once GitHub derives anchors from the translated heading text. Assembly now rewrites #fragment links in Markdown links, definitions and raw HTML hrefs to the slug of the heading at the same position, using github-slugger.
Closesberry-13/LibreChat#384
* 🧻 fix: Keep Lighthouse Session Cookies Out of Failure Logs
* ci: Use Lockfile-Pinned Chromium for Lighthouse
* ci: Align Lighthouse Browser Launch With Playwright
---------
Co-authored-by: Lia <lia@librechat.ai>
* 🚦 ci: Throttle Codegraph E2E Votes to One Run per Window
A vote runs the whole mock suite on ten runners, about 154 job-minutes, and
every merge to dev started one: 2,227 job-minutes on 2026-10-22, queued beside
PR CI for the same runners.
With repo variable CODEGRAPH_E2E_VOTE_MIN_HOURS set to N > 0, the votes
workflow skips its push runs (in a concurrency group of their own) and the new
Codegraph E2E Vote Gate decides instead: a merge starts a vote on dev
(workflow_dispatch) once the newest started vote is N hours old, and an hourly
catch-up votes the newest merge no vote covers once the window opens. A merge
votes as before while the catch-up has not run for three hours or the history
cannot be read. Unset, empty or 0 keeps today's push-triggered votes and skips
the gate; CODEGRAPH_E2E_VOTES=off still stops both.
The decision is a pure function in .github/scripts/vote-gate.mjs, tested in
vote-gate.test.mjs and run beside the shard tests in playwright-mock.yml.
* 🚦 fix: Keep an Unfinished Handoff Run from Covering Its Merge
With the throttle on, a merge creates the votes workflow's push run, whose
vote job will be skipped, and the gate's push run at about the same time.
Until that handoff run completed, the gate read it as a queued trial: it
matched the merge on head_sha, so the merge started no vote and waited for a
later catch-up tick, and it also held the window as a started vote.
While throttled, a push run that has not completed is now read as a handoff:
it neither covers a merge nor holds the window. A finished push run that
voted still counts as before.
The vote suite grew from 375 tests (39.1 min on one runner, 2026-09-30)
to 1,321, so a single-runner vote can no longer finish. Run it as the
same ten duration-planned shards playwright-mock.yml uses; each shard
logs the specs it executed and the codegraph shadow unions them into
one trial. A shard that runs out of its 28-minute test budget logs only
its failed specs, never clean ones.
* 💉 chore: Upgrade Node.js to Security Release 24.22.1
* test: Enable Enter Submission in Native Acceptance
* test: Use the Machine Picker in Native Acceptance
---------
Co-authored-by: Lia <lia@librechat.ai>
Each merge to dev cancelled the vote run before it, and the full mock
suite needs about 43 minutes, so 480 of 499 runs since 2026-09-24 never
finished (282 superseded, 153 cut by the 45-minute timeout, 45 never
started). Graduation evidence stopped at 09-30. Keep a started run and
one pending run, and raise the timeout to 75 minutes.
* test: Spec the First-Sentence Diagnostic Comparison in the Suppression Runner
* test: Copy the Diagnostics Module into the Suppression Spec Synthetic Roots
* test: Copy the Diagnostic Comparison Spec into the Suppression Synthetic Roots
Plan the complete mock suite's shards from recorded per-file durations instead of Playwright's equal-count split, widen the memory lanes from six to ten, and give the nightly full suite ten shards per store so it fits its 30-minute job timeout again.