Mux SDK versions.
The Mux packages Versyka recognizes on npm and PyPI, their latest releases, and where the breaking changes are documented. Monitoring checks connected repositories against these every day.
Packages we track
| Package | Registry | Latest | Status | Release notes |
|---|---|---|---|---|
@mux/ts | npm | 15.6.1 | Maintained | View → |
@mux/mux-node@mux/mux-node was renamed to @mux/ts; 15.5.0 is its final release. | npm | 15.5.0 | Deprecated | View → |
mux-python | PyPI | 5.1.2 | Maintained | View → |
Latest versions from the public npm and PyPI registries, checked and refreshed daily.
Mux SDK questions
What is the latest version of the Mux SDK?
As of 2026-10-26: @mux/ts 15.6.1 on npm; @mux/mux-node 15.5.0 on npm; mux-python 5.1.2 on PyPI.
Versions come from the public registries and are refreshed every day.
How do I upgrade the Mux SDK without breaking my code?
Read the release notes for every major version between yours and the latest, update each call that changed, then run your typecheck, build and tests.
- Versyka's free upgrade check shows which Mux packages in your package.json or requirements.txt are major versions behind, with the release notes.
- Versyka can do the upgrade for you: it finds every affected Mux call, rewrites it, runs your own tests and opens a pull request only if they pass.
Is @mux/mux-node deprecated?
Yes. @mux/mux-node is marked deprecated on npm: "@mux/mux-node was renamed to @mux/ts. 15.5.0 is the final release under this name; install @mux/ts for all future releases. Migration guide: https://github.com/muxinc/mux-ts/blob/main/MIGRATION.md"
Does Versyka monitor Mux SDKs?
Yes. Versyka recognizes @mux/ts (npm), @mux/mux-node (npm), mux-python (PyPI) in connected repositories and flags them every day when they fall a major version behind or are deprecated.
Behind on Mux?
Versyka finds every affected Mux call in your code, rewrites it, runs your tests and opens a pull request.