Skip to content

⬆️ chore: Bump LibreChat Packages & Add Locale Keys for New Config Fields#89

Merged
danny-avila merged 1 commit into
mainfrom
claude/quizzical-jemison-41ef8b
Jun 24, 2026
Merged

⬆️ chore: Bump LibreChat Packages & Add Locale Keys for New Config Fields#89
danny-avila merged 1 commit into
mainfrom
claude/quizzical-jemison-41ef8b

Conversation

@danny-avila

Copy link
Copy Markdown
Contributor

Summary

Updates the two LibreChat packages to their latest published versions:

Package Before After
@librechat/data-schemas ^0.0.55 ^0.0.56
librechat-data-provider ^0.8.508 ^0.8.509

New config fields

The new librechat-data-provider introduces three new fields in the config schema. Because the configuration editor is schema-driven, these surfaced automatically — and the localization coverage test (localization.test.ts) flagged the missing com_config_field_* locale keys. Added them so the editor renders proper labels instead of raw keys:

  • url_contextURL context (boolean toggle, sibling of web_search)
  • includeReasoningContentInclude reasoning content (under customParams, sibling of reasoningFormat/reasoningKey)
  • includeReasoningHistoryInclude reasoning history (under customParams)

Verification

All checks pass locally against the updated packages:

  • tsc --noEmit (type check)
  • eslint src/ --max-warnings 0 (lint)
  • vitest run — 732 tests passing (was failing 1 before the locale keys were added)
  • prettier --check

🤖 Generated with Claude Code

…elds

Update @librechat/data-schemas (0.0.55 → 0.0.56) and
librechat-data-provider (0.8.508 → 0.8.509).

The new data-provider adds three config schema fields, so add the
matching `com_config_field_*` locale keys to keep the schema-driven
config editor (and its localization coverage test) green:

- url_context → "URL context"
- includeReasoningContent → "Include reasoning content"
- includeReasoningHistory → "Include reasoning history"
@danny-avila danny-avila merged commit da1e2fc into main Jun 24, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants