* 🦠 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: 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: Patch minimatch and qs advisories in nested dev dependencies
* fix: Align Nodemon Dependency Regression With minimatch 11
---------
Co-authored-by: Lia <lia@librechat.ai>
- Bump @floating-ui/utils from 0.2.8 to 0.2.9 in package-lock.json and bun.lock so isContainingBlock treats translate, scale and rotate as containing blocks
- Add schedule-time-popover scenarios: the Weekly time picker, the Hourly minute picker and a dialog scrolled by its own overflow each open against their field
* chore: Add framer-motion and react-dnd as @librechat/chat Peers
* refactor: Move the Composer Queue Rail Into the Chat Package
* fix: Keep Store Atoms Out of the Queue Rail's Module Load
* refactor: Move Composer Input Controls and Shortcut Helpers Into @librechat/chat
* test: Cover Interrupt Now on a Queued Composer Row
* test: Read the Moved Escalate Button in the Composer Color Guardrail
* refactor: Reuse the Core Draft Check for the Send Button
* fix: Point the Acceptance Harness at the Moved Composer Shortcuts
splitMarkdown and editableParts move to packages/chat/src/core/parts and are
exported from the package root, so hasEditablePart is available to package
components. The micromark and mdast packages the splitter parses with become
peer and dev dependencies of @librechat/chat at the client's ranges, kept
external by the build, and the package jest config transforms them like the
client's does.
* refactor: Move Composer Attachment Components Into @librechat/chat
* test: Cover the Pasted Text Editor From Paste to Saved Edit
* test: Keep the Real Data Provider Enums in the ChatView Subagent Spec
* refactor: Build the Source Badge Styles at Render Time
* test: Reopen the Pasted Text Correction From Its Replacement Chip
* chore: Re-record the Attachment Design Suppressions on Dev
* test: Merge the SteerPart Package Mocks Into One Factory
* feat: Add a Minimal Consumer Example for @librechat/chat
A Vite React page under packages/chat/example renders a themed chat from the package's public entries and the @librechat/client theme, with an in-memory transport standing in for the server. Its jsdom smoke test runs in the package's jest suite, the package typecheck covers it, and ESLint keeps it to public imports and semantic theme roles.
* fix: Let Enter Confirm an IME Composition in the Example Composer
* fix: Report a Failed Turn in the Example and Restore Its Text
* fix: Localize the Example Copy and Guard the Safari IME Enter
* fix: Drop a Rejected Turn, Load the Component CSS, and Keep the i18n Instance in the Example Build
* refactor: Replace the Example App With a Public-Entry Consumer Spec
The owner does not want an example app in the repository. packages/chat/test/consumer.spec.tsx keeps what it proved: a chat built only from @librechat/chat, /react, /components and @librechat/client, over an in-memory transport, streams a reply into the message list under the ClickHouse theme. It sits outside src because chat/boundary rejects self-imports there; jest maps the entry names to the sources and the package typecheck covers it. The example app, its Vite, Tailwind and PostCSS config, its lint block, script and dependency lines are removed.
* chore: Declare the Consumer Spec's i18next Dev Dependencies
* chore: Retest Against Current Dev
* refactor: Add the Core Chat Class With a Serial Job Executor and React Query State
* fix: Report an Attachment's HTTP Failure as a Disconnect and the Turn's Conversation on Finish
* fix: Report a Stream That Fails While It Is Read as a Disconnect
* fix: Keep an Attachment Failure a Disconnect When the Host Reducer Throws on It
* fix: Treat a Resumed Start as an Attachment and Drop a Replaced Start's Optimistic Rows
* fix: Undo the Whole Optimistic Write of a Start the Server Replaced
* fix: Give Each Optimistic Write One Rollback Record and Stop a Disposed Chat Writing State
A turn keeps its optimistic write on the active request, so a disposal before the start was sent undoes those rows as a replaced start already did, and a removed row is restored next to its surviving neighbors instead of at its old index. A disposed chat no longer moves the shared status or connection, so a listener that disposes on a rollback notice cannot leave the state reconnecting. A start that fails with ERR_INTERNET_DISCONNECTED is a disconnect like ERR_NETWORK, and the React Query state rechecks a host store that changed between a version read and its subscription.
* fix: Roll Back the Rows a Store Committed, Not the Rows the Chat Handed It
A React Query cache with structural sharing commits a changed row as a copy, so a replaced start compared its rollback record against objects the cache never held and kept the optimistic edit. The record now takes the list as the state reads it back after the write.
* fix: Record the Optimistic Rows a Store Committed Before Telling Subscribers
A listener that writes the shared state when the chat announces its optimistic write no longer lands in that write's rollback record, so a replaced start keeps the listener's rows. The record is taken before anyone is notified, and a store's report of the chat's own write waits for the chat's announcement instead of running inside the write.
* fix: Stop a Stream Event Once a Listener Disposed the Chat on Its Write
A listener that disposes the chat while an event's write is announced no longer lets that event move the shared status to streaming or reach onEvent after teardown.
* fix: Scope Optimistic Rollback to the Rows the Write Itself Changed
The rollback record kept the whole list the store committed, so a row a store subscriber appended while the write was committed was undone with the turn, and a subscriber that disposed the chat inside the write left the turn's rows behind because no record existed yet. The record now holds, by message id, only the rows the write added, replaced or removed, each under the identity the store committed it with; undo restores or drops those and leaves every other row. A dispose inside the write is undone once the record exists.
* fix: Leave a Turn Row a Store Subscriber Edited Inside the Write Out of Its Rollback
A store that notifies its subscribers synchronously can hand back one of the turn's rows already edited by a subscriber, and the rollback of a replaced start then deleted or overwrote that edit. The record now claims a committed row only when it is the written row or a structural copy of it.
* chore: Update package dependencies across multiple modules
- Upgraded `@azure/identity` to version 4.14.0 in package.json files.
- Updated `multer` to version 2.5.0 and `nodemailer` to version 10.2.1.
- Incremented `undici` to version 7.30.1.
- Updated `@happy-dom/jest-environment` to version 21.0.4.
- Incremented `qs` to version 6.16.1 and `fast-uri` to version 3.1.9.
- Updated `serialize-javascript` to version 7.1.4.
- Updated `zod` to version 4.6.7 in multiple modules.
These updates ensure compatibility with the latest features and security improvements.
* chore: update bun.lock file
* chore: Update dompurify to version 3.4.17 across all package files
- Bumped dompurify version from 3.4.16 to 3.4.17 in package.json, package-lock.json, and relevant sub-packages.
- Ensured consistency in dependency versions across the project.
* chore: Update ip-address package to version 10.7.4 in package.json and package-lock.json
- Bumped ip-address version from 10.5.1 to 10.7.4 in package.json.
- Updated package-lock.json to reflect the new version and integrity hash.
* 🔧 chore: Update sanitize-html and related dependencies in package-lock.json and package.json
- Upgrade sanitize-html from ^2.17.7 to ^2.18.1 across multiple package.json files.
- Update dayjs from 1.11.21 to 1.11.23 in package-lock.json.
- Upgrade is-plain-object from 5.0.0 to 5.1.0 in package-lock.json.
- Upgrade launder from 1.7.1 to 1.7.2 in package-lock.json.
- Update postcss from ^8.3.11 to ^8.5.27 in package-lock.json.
* 🔧 chore: Upgrade mongodb-memory-server to version 11.3.0 across package-lock.json and multiple package.json files
- Update mongodb-memory-server from ^11.0.1 to ^11.3.0 in package-lock.json.
- Reflect the same version change in api/package.json and packages/data-schemas/package.json.
* 🔧 chore: Upgrade hono to version 4.13.13 in package.json and package-lock.json
- Update hono from ^4.13.7 to ^4.13.13 in package.json.
- Reflect the same version change in package-lock.json.
* 🔧 chore: Upgrade follow-redirects to version 1.16.1 in package-lock.json
- Update follow-redirects from 1.16.0 to 1.16.1 in package-lock.json.
- Upgrade Vite from ^8.2.2 to ^8.3.5 in both package-lock.json and package.json.
- Update @oxc-project/types version from 0.147.0 to 0.155.0 in package-lock.json.
- Change funding URL for @oxc-project/types in package-lock.json.
- Upgrade multiple @rolldown/binding packages from version 1.2.6 to 1.2.15 in package-lock.json.
* fix: Mirror Shared Primitives For RTL Layouts
* fix: Import the Direction Helper Relatively in InfoHoverCard
* test: Cover Mirrored Switch and Dialog Close in RTL
* fix: Keep the Focused Sign-In Label Inside Its Field in RTL
* fix: Mirror by Element Direction and Re-Resolve Side Placement on Open
* test: Pin RTL Scenarios to the Element Direction and Expect a Trailing Number Input
* fix: Keep Time Column Arrow Keys Vertical in RTL
* fix: Keep :dir() Selectors Through CSS Minification
* chore: Declare lightningcss for the Client Build Config
* fix: Keep SelectDropDown Left and Right Icon Sides Physical
* fix: Fall Back to the dir Attribute Where :dir() Is Unsupported
* fix: Leave Nested LTR Islands Unmirrored in the dir Attribute Fallback
* fix: Resolve the Slider Direction From Its Nearest dir
* fix: Resolve the Nearest dir at Any Depth in the :dir() Fallback
* fix: Re-Resolve the Slider Direction When a dir Attribute Changes
* fix: Keep the Provider Direction for a Slider Without a dir Ancestor
* fix: Read an Automatic dir From the Computed Direction for the Slider
* fix: Prefer the Computed Direction When Resolving an Element's Direction
* fix: Re-Resolve the Slider Under a dir=auto Boundary When Its Content Changes
* fix: Keep the Mirrored Combobox Placement Across Rerenders
* refactor: Let the Slider Read Its Direction From the Radix Provider
* fix: Space a Trailing Combobox Option Icon From Its Label
* fix: Follow the Interface Direction in Radix, the Composer and First Paint
Wrap the app in a Radix DirectionProvider driven by i18n so Tabs, Select and
menus stop rendering LTR subtrees in right-to-left locales, and swipe toasts
toward the inline end.
Chat direction becomes auto, ltr or rtl (auto by default; stored LTR/RTL
values are kept). The composer applies a forced direction as a dir attribute
instead of reversing rows, which double-flipped under an RTL document, and the
text fields default to dir=auto. The unused Jotai chat direction atom that
pinned every TextareaAutosize to ltr is removed.
index.html sets dir before first paint, and the language setting no longer
races i18n over document.lang.
* fix: Keep the Empty Composer Placeholder on the Interface's Reading Edge
* fix: Hash Off the Event Loop and Surface API Key Lookup Failures
Registration, email verification, password reset and verification resends
hashed and compared with bcryptjs's synchronous calls. bcryptjs is pure
JavaScript, so each call blocked the event loop for every request in the
process. They now use the promise APIs, and the password reset
dependencies are async.
validateAgentApiKey caught its own query failures and returned null, so a
database outage answered remote callers with 401 Invalid API key. It now
lets the failure reach requireApiKeyAuth, which answers with a 500.
* fix: Run bcrypt on a Worker Pool in packages/api
bcryptjs's promise API still computes on the main thread, only in chunks
of up to 100 ms, so concurrent registrations and resets kept stalling
unrelated requests (four cost-10 hashes delayed a 5 ms timer by about
190 ms). hashSecret and compareSecret now run bcryptjs on a small
worker_threads pool in packages/api, and AuthService.js calls them.
* feat: Configure the Password Hashing Worker Count
* fix: Verify Login and Step-Up Passwords on the Hash Pool
* 🧵 test: Cover Harmony Headers in Text Attachments Sent to OpenAI Models on Bedrock
A pasted text/plain attachment is sent inline as file context, so a harmony header such as `<|channel|>analysis` inside it reaches every later turn. OpenAI models on Bedrock answer that request with an event stream that closes before any event, which crashed the turn in @librechat/agents 4.0.4 with `Cannot use 'in' operator to search for 'tool_calls' in undefined`.
Drive LibreChat's own file-context formatting through the SDK's Bedrock model with a recorded response and assert the header reaches an OpenAI model neutralized and other model families unchanged.
* 📦 chore: Bump @librechat/agents to v4.0.5
* 📦 chore: Regenerate the Lockfile with npm 11 to Keep libc Constraints
* refactor: Remove Unused Agent Helpers and Superseded Wrappers
* refactor: Remove Dead Auth, Middleware, Protection and Prompt Helpers
* refactor: Remove Dead MCP, File, Skill and Endpoint Code
* refactor: Remove Dead Stream, Telemetry, Utility and Type Exports
* chore: Drop Unused packages/api Dependencies From bun.lock
* refactor: Keep Published Compatibility and Deprecated packages/api Exports
Bump @modelcontextprotocol/sdk from ^1.30.0 to ^1.32.1 in api and
packages/api. 1.31.0 binds stored OAuth credentials to the issuing
authorization server; LibreChat does not use the affected auth()/
authProvider path and already pins refreshes to the stored token endpoint.
1.32.0 makes the client transports follow same-origin redirects
themselves, which would re-issue requests the connection fetch declined
(hop cap, reauthorized tools/call). Set redirectPolicy: 'follow' so
redirects stay with the connection fetch, and cover both transports with
real-SDK tests.
* refactor: Move text-like message parts into @librechat/chat
Text, EmptyText, CollapsibleText, Summary and AgentUpdate move into the package's components entry with their unit specs and read the app only through MessagePartsHost, which gains renderMarkdown, useSmoothStreaming, useAgent and renderAgentIcon. The app's markdown and agent-icon renderers register from the Parts barrel, so the host module keeps its import graph.
The design-suppression runner compares a moved file's diagnostics by their first sentence: the remedy that follows names app-only compositions for client paths, so the same violation read as new after a move.
* test: Cover text-like parts rendered from @librechat/chat in the browser