Skip to content

馃殌 v0.8.8 - #15735

Open
danny-avila wants to merge 1 commit into
devfrom
danny-avila/release-v0.8.8-rc3
Open

馃殌 v0.8.8#15735
danny-avila wants to merge 1 commit into
devfrom
danny-avila/release-v0.8.8-rc3

Conversation

@danny-avila

@danny-avila danny-avila commented Sep 8, 2026

Copy link
Copy Markdown
Owner

Summary

Prepare LibreChat v0.8.8 by updating the application and publishable package versions, Config 1.3.16, Helm chart 2.0.10, lockfiles, and the README feature summary. The release commit is based directly on current dev and includes the latest Agent, Code workspace, Scheduled Chat, MCP, attachment, navigation, context usage, security, and reliability changes.

Change Type

  • This change requires a documentation update

Testing

  • 451 focused data-provider config, file-routing, and file-schema tests pass
  • helm lint helm/librechat passed before the fresh-rebase worktree lost its vendored chart dependencies
  • Version, lockfile, and changelog coverage checks pass for all 946 PRs and direct commits through current dev
  • git diff --check passes
  • The data-schemas retention/migration tests could not start against the reused RC2 dependency tree because it lacks newly required exports and winston-daily-rotate-file; CI will run them with current dependencies

Checklist

  • My code adheres to this project's style guidelines
  • I have performed a self-review of my own code
  • I have made pertinent documentation changes
  • My changes do not introduce new warnings
  • Local focused unit tests pass with my changes
  • A pull request for updating the documentation has been submitted: 馃殌 v0.8.8聽LibreChat-AI/librechat.ai#763

@danny-avila
danny-avila force-pushed the danny-avila/release-v0.8.8-rc3 branch 8 times, most recently from 7e03faa to 3551552 Compare September 11, 2026 20:59
@danny-avila danny-avila changed the title 馃殌 v0.8.8-rc3 馃殌 v0.8.8 Sep 11, 2026
@danny-avila
danny-avila force-pushed the danny-avila/release-v0.8.8-rc3 branch from 3551552 to abb4ec3 Compare September 12, 2026 12:47
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.

1 participant