* chore: bump packages
* chore: bump packages
* chore: bump packages
* chore: update package dependencies to latest versions
* chore: update configuration and dependencies for Nextra migration
- Updated TypeScript references in `next-env.d.ts` to align with new Nextra structure.
- Modified `next.config.mjs` to ignore ESLint and TypeScript build errors during the build process.
- Added a new `PACKAGE_UPDATE_SUMMARY.md` documenting package updates and migration details.
- Downgraded Next.js and Nextra versions for compatibility, and updated related dependencies.
- Introduced new `page.tsx` files for dynamic routing and metadata generation in the app directory.
- Added 'use client' directive to multiple components to support client-side rendering.
- Refactored components to remove deprecated Nextra context methods in preparation for App Router.
* chore: update ESLint configuration to use __dirname for tsconfigRootDir and fix lint errors
* chore: update initial statistics for GitHub stars and Docker pulls in Usage component
* chore: refactor clean-cache script to use CommonJS require syntax
* chore: remove redundant ESLint installation step in workflow
Updated documentation to reflect changes from LibreChat PR #10355, which fixed Azure OpenAI Speech-to-Text 400 Bad Request errors by adding support for the new `.cognitiveservices.azure.com` domain format alongside the legacy `.openai.azure.com` format.
Changes:
- Added domain format support callouts in STT/TTS configuration documentation
- Updated Azure OpenAI configuration guide with new endpoint format examples
- Enhanced instanceName field descriptions across all Azure configuration docs
- Updated DALL-E baseURL documentation to show both domain formats
- Added examples demonstrating both legacy and new domain usage
All changes maintain backward compatibility while documenting the new functionality.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-authored-by: Claude <noreply@anthropic.com>
* docs: Add OIDC Group Synchronization documentation for Keycloak
Add comprehensive documentation for the new OIDC group sync feature:
- Overview and prerequisites
- Configuration examples for realm roles, client roles, and groups
- Step-by-step setup instructions
- Troubleshooting guide with common claim paths
- Usage examples for permissions
- Limitations and best practices
Covers integration with LibreChat's granular permissions system
for agents, prompts, files, and conversations.
Related to LibreChat PR and issue #10006
* docs: Add group/role exclusion pattern documentation
Document OPENID_GROUPS_EXCLUDE_PATTERN configuration option:
- Explain exact match (case-insensitive) and regex pattern support
- Provide common Keycloak exclusion examples
- Show why to exclude system roles, default roles, and auth roles
- Add practical scenario with admin/developers vs system roles
- Include configuration examples for filtering out:
- offline_access, uma_authorization (system roles)
- default-roles-* (default realm roles)
- manage-account, view-profile (account management)
Complements the group sync feature by allowing fine-grained control
over which roles become groups in LibreChat.
- Introduced `context` capability for agents endpoint, enabling file uploads in chat.
- Enhanced `fileConfig` with OCR, text parsing, STT separation, and `fileTokenLimit` parameter.
- Added `transactions` object structure for token usage tracking.
- Included `jinaApiUrl` in `webSearch` configuration for custom Jina instances.
- Updated documentation for `fileConfig` to reflect new fields and processing methods.
- Added type definitions for the BlogCard component props.
- Updated tsconfig.json to include new libraries and strict null checks.
- Modified next-env.d.ts to reference additional Next.js navigation types.
Having the version id results with the warning - the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
* 📚 docs: Add OCR, textParsing, and fileTokenLimit configuration documentation (#376)
- Added support for `ocr` and `textParsing` configurations in `fileConfig`, allowing users to specify file types for OCR processing and direct text extraction.
- Introduced `fileTokenLimit` parameter for all endpoints to manage maximum token limits for file processing.
* 📚 docs: Add STT configuration documentation (#380)
- Added `stt` configuration to `fileConfig` for Speech-to-Text audio file processing, including supported MIME types.
- Updated changelog to reflect the addition of STT alongside existing OCR and text parsing configurations.
* 📚 docs: finish fileTokenLimit documentation and update changelog (#382)
* refactor: change `textParsing` to `text`
* docs: Enhance dotenv.mdx with MongoDB connection pool and schema configuration options
- Added new sections for MongoDB connection pool configuration, detailing options like MONGO_MAX_POOL_SIZE and MONGO_MIN_POOL_SIZE.
- Introduced MongoDB schema configuration options, including MONGO_AUTO_INDEX and MONGO_AUTO_CREATE.
- Provided usage examples and explanations for each new option to improve clarity and usability.
* docs: Add Microsoft Graph API integration details for Azure Entra ID
- Introduced new sections in dotenv.mdx and azure.mdx for Microsoft Graph API integration, enhancing permissions and sharing capabilities with people and group search features.
- Added prerequisites and configuration steps for enabling Graph API permissions in Azure app registration.
- Updated token-reuse.mdx to include information on Microsoft Graph API integration when using Azure Entra ID with token reuse.
* docs: Add OPENID_GENERATE_NONCE environment variable to dotenv.mdx
- Introduced the OPENID_GENERATE_NONCE variable, which forces the OpenID client to generate a nonce parameter, addressing requirements from identity providers like AWS Cognito and Authentik.
- Updated documentation to enhance clarity on its usage and importance in OpenID configurations.
* docs: Add SharePoint integration details and configuration instructions
- Introduced a new section in dotenv.mdx for SharePoint integration, detailing environment variables required for enabling the SharePoint file picker.
- Added comprehensive documentation in sharepoint.mdx covering the integration process, prerequisites, and user experience for accessing SharePoint files within LibreChat.
- Updated azure.mdx with additional information on SharePoint permissions needed for Azure app registration.
- Enhanced existing documentation to clarify the setup and usage of SharePoint features, ensuring users can effectively utilize this enterprise capability.
* docs: Add file citation configuration for agents endpoint in v1.2.9
- Introduced new file citation settings (`maxCitations`, `maxCitationsPerFile`, `minRelevanceScore`) to enhance control over citation quality and quantity in agent responses.
- Updated interface configuration to include `fileCitations`, enabling display of file citations during file search functionality.
- Added detailed documentation for the new configuration options in the changelog and relevant sections of the documentation.
* docs: Update fileCitations configuration details in v1.2.9
- Revised the description of the `fileCitations` setting to clarify its role as a global toggle for the `FILE_CITATIONS` permission, affecting all users regardless of individual permissions.
- Enhanced documentation in both the changelog and interface configuration sections to reflect these changes and improve user understanding of citation display behavior during file searches.
* docs: Add USE_REDIS_CLUSTER environment variable to Redis configuration
- Introduced the USE_REDIS_CLUSTER variable in dotenv.mdx to enable Redis cluster mode when using a single URI.
- Updated redis.mdx to include usage instructions for the new variable, enhancing clarity on Redis cluster configurations.
* chore: remove non-existant image reference
* chore: add missing code block language
* docs: Add migration instructions for agent permissions in v0.8.0-rc3+
- Introduced a new section detailing the migration to an ACL-based permission system for agents, including permission levels (OWNER, EDITOR, VIEWER).
- Provided step-by-step commands for running the migration based on different deployment methods (docker-compose, deploy-compose, local development).
- Explained the implications of the migration on existing agents and included a note on prompt permissions migration.
