Motrix 2.0.0-beta.49

English | 简体中文

Motrix 2.0.0-beta.49 improves plugin installation and runtime setup, removes
shadows from plugin installation cards, and shows the automatic v1 Migration
Assistant only once.

Highlights

• Compatible plugins can be installed before FFmpeg is configured. Missing or
  incompatible FFmpeg is explained when enabling or running the plugin, while
  the installation consent notice remains advisory. Signature, manifest,
  permission and host-version checks remain in place
  (#2368).
• Configuring FFmpeg and refreshing detection updates plugin operations without
  restarting Motrix. Older detection results cannot replace newer runtime
  availability, and late enable checks cannot undo a subsequent disable,
  update or uninstall. Plugin switches follow the host state
  (#2368).
• The uninstalled-plugin detail page uses flat, bordered cards without shadows
  (#2368).
• Detecting Motrix v1 offers automatic migration once. If you leave or close the
  app without choosing import or skip, later starts no longer redirect to the
  assistant. Migration remains available from the sidebar
  (#2368).

Before testing

This is prerelease software. Back up existing Motrix data and downloads before
installing it. When practical, test v2 with a separate OS account, machine or
Docker data directory.

Media Merge remains an optional plugin installed separately. Configure FFmpeg
in Settings → Integration → Media Tools before enabling or running it.
Installing a plugin does not grant arbitrary file access: operations still
require selected inputs and a confirmed output, and Web operations remain
subject to Server operator policy. No plugin or SDK update is required for
these host fixes.

The Migration Assistant does not import or resume downloads automatically.
Manual migration preserves original files and imports selected tasks as paused
records; legacy progress import remains unavailable on Windows.

Renderer recovery remains manual. Broader Windows/Linux sleep, GPU-fault and
long-running recovery acceptance is still pending. This release does not add
unsupported IPv6-literal SOCKS targets to plugin networking; such requests
continue to fail without falling back to a direct connection.

After the protected Snap workflow completes, install the strictly confined build
with sudo snap install motrix --edge. Installations tracking latest/edge
should upgrade to the beta.49 revision set.

Planned downloads after release gates pass

After every container gate passes, use
docker.io/motrixapp/motrix-server:2.0.0-beta.49 or
ghcr.io/agalwood/motrix-server:2.0.0-beta.49. See the
Docker Server guide
for storage, networking, and upgrades.

Distribution notes

• Flatpak bundles use application ID app.motrix.native and the beta branch.
  Install each new bundle with flatpak install --user --or-update; these files
  do not configure a Motrix update remote. Update the Native Host companion
  separately. See the Flatpak guide.
• AppImage desktop integration remains opt-in. Browser cold launch requires the
  separately enabled Native Messaging host and a registered AppImage path;
  reconnecting to a saved pairing also requires a compatible Extension.
• Windows arm64 and all 32-bit app packages are unavailable. Windows packages
  are unsigned and may trigger SmartScreen; use the official published GitHub
  prerelease.
• Beta container tags are immutable and do not change latest, stable, or
  other stable-channel aliases. Snap publication updates latest/edge only.

Feedback

Report reproducible problems through
GitHub Issues, including your OS,
architecture, package type and reproduction steps.

What's Changed

• fix(app): defer plugin runtime checks and show migration once by @agalwood in #2368
• chore(release): prepare 2.0.0-beta.49 by @agalwood in #2369

Full Changelog: v2.0.0-beta.48...v2.0.0-beta.49