Merged
Conversation
suyanhanx
approved these changes
Apr 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #.
Rationale for this change
The current Seafile fixture is pinned to an older 11.x layout because the newer Docker images no longer work with the legacy
memcached + inline envsetup. This PR migrates the fixture to the official 13.x deployment structure so CI can validate the Seafile backend against a current, supported image again.What changes are included in this PR?
The fixture now uses the minimal official 13.x topology (
mariadb + redis + seafile) with an explicit env file checked into the repository. The GitHub Action loads that env file and resets compose state before startup so each run gets a clean Seafile instance.Are there any user-facing changes?
No user-facing changes.
AI Usage Statement
N/A