Skip to content

Sync upstream LibreChat v0.8.8-rc4 - #16381

Closed
stcuthbertscollege wants to merge 8 commits into
LibreChat-AI:devfrom
stcuthbertsnz:sync/upstream-main
Closed

stcuthbertscollege wants to merge 8 commits into
LibreChat-AI:devfrom
stcuthbertsnz:sync/upstream-main

Conversation

@stcuthbertscollege

Copy link
Copy Markdown

Summary

  • Merge upstream/main (v0.8.8-rc4) into the St Cuthbert's fork, catching up ~747 upstream commits from rc1.
  • Resolve permission conflicts by keeping both upstream SCHEDULES and our fork's CONVERSATIONS.DELETE.
  • Preserve school-specific deploy customizations: branding favicons, admin-panel on 127.0.0.1:3000, production nginx/SSL for chat.stcuthberts.college, and DEPLOYMENT.md.

Test plan

  • Confirm conflict resolution: SCHEDULES and CONVERSATIONS.DELETE both present in permissions/roles schemas
  • Confirm deploy-compose.yml still bind-mounts branding and binds admin-panel to localhost only
  • Confirm client/nginx.conf still has chat.stcuthberts.college SSL blocks
  • Confirm conversation Delete menu item still gated by PermissionTypes.CONVERSATIONS / Permissions.DELETE
  • Smoke-test app against updated images/config after deploy (note: droplet still runs registry images, not this fork's build)

Made with Cursor

stcuthbertscollege and others added 8 commits August 18, 2026 04:06
Adds a CONVERSATIONS.DELETE role permission (default true for ADMIN/USER)
and hides the sidebar Delete menu item when the current user's role lacks
it, so specific roles (e.g. students) can be restricted without a code
change. Includes a one-off script to flip the permission for a role.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…e-permission

Gate conversation delete behind a per-role permission
Documents the fork/upstream layout, the manual droplet update process,
tracked droplet-specific config, and Entra ID OpenID role-sync gotchas
so this knowledge isn't only in one person's head.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…e-permission

docs: add deployment and sync runbook
Bring fork from v0.8.8-rc1 to rc4 while keeping CONVERSATIONS.DELETE
alongside upstream SCHEDULES permissions.

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions
github-actions Bot changed the base branch from main to dev September 25, 2026 20:07
@github-actions

Copy link
Copy Markdown
Contributor

👋 Thanks for the contribution! LibreChat merges all changes into dev first — main only moves at release time — so this pull request's base branch was switched from main to dev automatically.

Nothing is needed from you; your commits, reviews and discussion are unchanged. If the diff now shows files you did not touch, rebase onto dev:

git remote add upstream https://github.com/LibreChat-AI/LibreChat.git
git fetch upstream dev
git rebase upstream/dev
git push --force-with-lease

Maintainers: apply the target: main label and restore the base branch if this one genuinely belongs on main.

@stcuthbertscollege

Copy link
Copy Markdown
Author

Opened against upstream by mistake — this sync is intended for the stcuthbertsnz/LibreChat fork only. Closing.

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