Conversation
Bumps both smp-server and xftp-server images to v7.0.1 (published to Docker Hub for amd64 and arm64 on 2026-07-31). Upstream's only change affecting this package is an SMP server fix: the server no longer creates an internal message queue when relaying messages as a proxy for private routing, where it was never drained and could leak memory and stall message processing. The release's other change is to the notification server, which this package does not ship; xftp-server has no code changes. start-sdk is already at 2.0.9 (latest) and tor-startos#next is already at its tip, so no dependency changes ride along.
MattDHill
approved these changes
Aug 3, 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
2 participants
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.
Summary
Bumps SimpleX to 7.0.1 —
7.0.0:0→7.0.1:0.Both images move in lockstep per
UPDATING.md:simplexchat/smp-serverv7.0.0v7.0.1simplexchat/xftp-serverv7.0.0v7.0.1Upstream check
v7.0.1is the newest plainvX.Y.Ztag onsimplex-chat/simplexmq. AsUPDATING.mdwarns, it is flagged a GitHub pre-release — the tag-list filter is the authority here, notgh release view.Both Docker images are published for
amd64andarm64(2026-07-31):simplexchat/smp-server:v7.0.1→sha256:7d825822839a…simplexchat/xftp-server:v7.0.1→sha256:69a7f95746bb…What's in the release
v7.0.0...v7.0.1is three commits. Only one is reachable from what this package ships:smpAgentCfg.msgQSizeis nowNothingfor the server. This is live for our users — the SMP server relays for private routing, and thetor-settingsaction wires a SOCKS proxy into[PROXY] socks_proxyfor exactly that path.ntf-serveris not shipped by this package.xftp-serverhas no code changes in this release; its image is rebuilt at the new version to keep the pins in lockstep.Upstream's
CHANGELOG.mdhas not been updated past 6.5.1, so the release notes link to the GitHub release page.Dependencies
No changes rode along:
@start9labs/start-sdkis already at 2.0.9, the latest on npm.tor-startos#nextis already pinned at its tip (aa867cf). Git deps were dropped frompackage-lock.jsonand re-resolved anyway to confirm — the lock came back byte-identical and is stable across repeated installs, with zero nested@start9labs/start-sdkcopies.Test plan
npm run check(tsc) — green.prettier --checkon both touched files — clean.v7.0.1image tags verified to resolve on Docker Hub forx86_64andaarch64before pinning.current.tsis edited in place at7.0.1:0andmigrationsstays empty.7.0.1adds on top of the7.0.0:0release already onmaster.Not run per monitor-cycle policy:
make/ Docker builds / s9pk pack.