Repository navigation
deploy: pin WuKongIM WAL recovery image [skip deploy] - #179
Merged
Merged
Conversation
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.
Pins only the WuKongIM service to the image built from c9f2da1, which backports validated compacted-WAL recovery from upstream0194a738. Server, gateway, Notebook, product migration43 and LingxiOS3.5.2 remain unchanged.
The owning Compose file passes
docker compose config --quietwith existing variables injected in memory. Merge/deployment waits for successful image workflow39025425390, including the upstream raftstore regression suite inside the Docker build. Onlylingxiloop-core-state/wukongimwill be redeployed through Komodo after immutable image verification. The existing IM volume and cold backup are retained; no database reset, WAL truncation, checksum rewrite or application rollback is performed.