Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Releases: MetaCubeX/mihomo

Prerelease-Alpha

12 Aug 17:01
@github-actions github-actions
Prerelease-Alpha
6bffbdd

Choose a tag to compare

View all tags
Prerelease-Alpha Pre-release
Pre-release

Release created at Tue Oct 28 18:50:18 CST 2025
Synchronize Alpha branch code updates, keeping only the latest version


ζˆ‘εΊ”θ―₯δΈ‹θ½½ε“ͺδΈͺζ–‡δ»Ά? / Which file should I download?
δΊŒθΏ›εˆΆζ–‡δ»Άη­›ι€‰ / Binary file selector
ζŸ₯ηœ‹ζ–‡ζ‘£ / Docs

Loading

v1.19.15

14 Oct 18:07
@github-actions github-actions
v1.19.15
c5fe367

Choose a tag to compare

View all tags
v1.19.15 Latest
Latest

What's Changed

BUG & Fix

Maintenance

Full Changelog: v1.19.14...v1.19.15

Contributors

wwqgtxx
Assets 123

v1.19.14

24 Sep 09:18
@github-actions github-actions
v1.19.14
fdc46f0

Choose a tag to compare

View all tags
v1.19.14

What's Changed

  • 0ced98d feat: support sending ping requests via direct in tun mode by @wwqgtxx

  • 0dc5e30 feat: add mTLS support for client & server (certificate and private-key for proxies, client-auth-type and client-auth-cert for listeners( by @wwqgtxx

  • 571be85 feat: support mieru 0-RTT handshake (#2261) by @enfein

  • 6786705 feat: remove ca and ca-str in hy1/hy2/tuic outbound, using fingerprint instead by @wwqgtxx

  • 80a90f0 feat: support AmneziaWG v2.0 by @wwqgtxx

  • 9a124a3 feat: add disable-icmp-forwarding option to tun (#2248) by @Nuofang

  • abe6c3b feat: support kcptun plugin for ss client/server by @wwqgtxx

  • For macOS users: According to the Go wiki, Go 1.25 no longer supports macOS 11. macOS 11 users are advised to download the binary with the go124 tag, macOS 10.15 users are advised to download the binary with the go122 tag, and macOS 10.13 users are advised to download the binary with the go120 tag.

  • Note: For amd64 platform, -amd64 and -amd64-compatible versions have been deprecated. -amd64-v1, -amd64-v2 and -amd64-v3 will be used to mark the CPU level. Please adapt the automatic update script in time for downstream projects.

BUG & Fix

Maintenance

Full Changelog: v1.19.13...v1.19.14

Contributors

wwqgtxx, enfein, and 3 other contributors
Loading

v1.19.13

27 Aug 09:42
@github-actions github-actions
v1.19.13
84086a6

Choose a tag to compare

View all tags
v1.19.13

⚠️⚠️ Warning: Any GUI client with the word mihomo in its name is not related to this project and violates the license agreement. Please do not use these malicious software. ⚠️⚠️

What's Changed

  • 1b0c72b feat: support vless encryption by @wwqgtxx client doc server doc

  • 5f09db2 feat: support AmneziaWG v1.5 by @wwqgtxx doc

  • dc52c38 fix: ? in DOMAIN-WILDCARD should match exactly one character #2204 by @wwqgtxx

  • For macOS users: According to the Go wiki, Go 1.25 no longer supports macOS 11. macOS 11 users are advised to download the binary with the go124 tag, macOS 10.15 users are advised to download the binary with the go122 tag, and macOS 10.13 users are advised to download the binary with the go120 tag.

  • Note: For amd64 platform, -amd64 and -amd64-compatible versions have been deprecated. -amd64-v1, -amd64-v2 and -amd64-v3 will be used to mark the CPU level. Please adapt the automatic update script in time for downstream projects.

BUG & Fix

Maintenance

Full Changelog: v1.19.12...v1.19.13

Contributors

wwqgtxx, enfein, and 2 other contributors
Loading

v1.19.12

27 Jul 13:50
@github-actions github-actions
v1.19.12
5f1f296

Choose a tag to compare

View all tags
v1.19.12

What's Changed

  • 241ae92 feat: support DOMAIN-WILDCARD rule (#2124) by @ayanamist
  • Note: For amd64 platform, -amd64 and -amd64-compatible versions have been deprecated. -amd64-v1, -amd64-v2 and -amd64-v3 will be used to mark the CPU level. Please adapt the automatic update script in time for downstream projects.

BUG & Fix

Maintenance

Full Changelog: v1.19.11...v1.19.12

Contributors

ayanamist, wwqgtxx, and 5 other contributors
Loading

v1.19.11

25 Jun 12:41
@github-actions github-actions
v1.19.11
5b97527

Choose a tag to compare

View all tags
v1.19.11

What's Changed

  • 29a37f4 feat: all dns client support disable-ipv4 and disable-ipv6 params by @wwqgtxx
  • 40587b6 feat: all dns client support skip-cert-verify params by @wwqgtxx
  • 617fef8 feat: converter support anytls/socks/http (#2100) by @beck
  • 85e6d25 feat: all dns client support ecs and ecs-override params by @wwqgtxx
  • 9283cb0 feat: add loopback-address support for tun by @wwqgtxx
  • Other incompatible updates are the same as v1.19.6~v1.19.10:
  • For security reasons, all paths appearing in the configuration file will be limited to workdir (regardless of whether they are relative or absolute). If there is a specific need, please specify additional safe paths by setting the SAFE_PATHS environment variable while ensuring safety. The syntax of this environment variable is the same as the PATH environment variable parsing rules of this operating system (i.e., semicolon-separated under Windows and colon-separated under other systems)
  • For security reasons, the "path" parameter of /configs in the restful api has been restricted, and its directory also needs to be in workdir or SAFE_PATHS.
  • In addition, support for specifying routing-mark and interface-name for proxy-groups has been removed. Please specify the relevant parameters in proxies directly.
  • Note: The workdir mentioned above is specified by the -d parameter when the program is started or the CLASH_HOME_DIR environment variable. If neither of the above is specified, the default is:
    • on Unix systems, $HOME/.config/mihomo.
    • on Windows, %USERPROFILE%/.config/mihomo.
  • The DNS resolution of the overall UDP part has been delayed to the connection initiation stage. It will be triggered only when the IP rule without no-resolve is matched during the rule matching process.
    • For direct and wireguard outbound, the same logic as the TCP part will be followed, that is, when direct-nameserver (or DNS configured by wireguard) exists, the resolution result in the rule matching process will be discarded and the domain name will be re-resolved. This re-resolution logic is only effective for fakeip.
    • For reject and DNS outbound, no resolution is required.
    • For other outbound, resolution will still be performed when the UDP connection is initiated, and the domain name will not be sent directly to the remote server.

BUG & Fix

Maintenance

Full Changelog: v1.19.10...v1.19.11

Contributors

beck, ayanamist, and 3 other contributors
Loading

v1.19.10

31 May 07:57
@github-actions github-actions
v1.19.10
c0f452b

Choose a tag to compare

View all tags
v1.19.10

What's Changed

  • The DNS resolution of the overall UDP part has been delayed to the connection initiation stage. It will be triggered only when the IP rule without no-resolve is matched during the rule matching process.
    • For direct and wireguard outbound, the same logic as the TCP part will be followed, that is, when direct-nameserver (or DNS configured by wireguard) exists, the resolution result in the rule matching process will be discarded and the domain name will be re-resolved. This re-resolution logic is only effective for fakeip.
    • For reject and DNS outbound, no resolution is required.
    • For other outbound, resolution will still be performed when the UDP connection is initiated, and the domain name will not be sent directly to the remote server.
  • In addition, the memory usage of the UDP part of tun inbound has also been optimized in this version.
  • Other incompatible updates are the same as v1.19.6~v1.19.8:
  • For security reasons, all paths appearing in the configuration file will be limited to workdir (regardless of whether they are relative or absolute). If there is a specific need, please specify additional safe paths by setting the SAFE_PATHS environment variable while ensuring safety. The syntax of this environment variable is the same as the PATH environment variable parsing rules of this operating system (i.e., semicolon-separated under Windows and colon-separated under other systems)
  • For security reasons, the "path" parameter of /configs in the restful api has been restricted, and its directory also needs to be in workdir or SAFE_PATHS.
  • In addition, support for specifying routing-mark and interface-name for proxy-groups has been removed. Please specify the relevant parameters in proxies directly.
  • Note: The workdir mentioned above is specified by the -d parameter when the program is started or the CLASH_HOME_DIR environment variable. If neither of the above is specified, the default is:
    • on Unix systems, $HOME/.config/mihomo.
    • on Windows, %USERPROFILE%/.config/mihomo.

BUG & Fix

Maintenance

Full Changelog: v1.19.9...v1.19.10

Contributors

wwqgtxx
Loading

v1.19.9

22 May 02:50
@github-actions github-actions
v1.19.9
fd959fe

Choose a tag to compare

View all tags
v1.19.9

What's Changed

  • 188372c feat: add tls.ech-key for external-controller-tls by @wwqgtxx
  • 5cf0f18 feat: reality add support-x25519mlkem768, it only works with new version server by @wwqgtxx
  • a1350d4 feat: add ech-key for listeners by @wwqgtxx
  • c6d7ef8 feat: add ech-opts for anytls/shadowsocks/trojan/vmess/vless outbound by @wwqgtxx
  • dc958e6 feat: add ech-opts for hysteria/hysteria2/tuic outbound by @wwqgtxx
  • Other incompatible updates are the same as v1.19.6~v1.19.8:
  • For security reasons, all paths appearing in the configuration file will be limited to workdir (regardless of whether they are relative or absolute). If there is a specific need, please specify additional safe paths by setting the SAFE_PATHS environment variable while ensuring safety. The syntax of this environment variable is the same as the PATH environment variable parsing rules of this operating system (i.e., semicolon-separated under Windows and colon-separated under other systems)
  • For security reasons, the "path" parameter of /configs in the restful api has been restricted, and its directory also needs to be in workdir or SAFE_PATHS.
  • In addition, support for specifying routing-mark and interface-name for proxy-groups has been removed. Please specify the relevant parameters in proxies directly.
  • Note: The workdir mentioned above is specified by the -d parameter when the program is started or the CLASH_HOME_DIR environment variable. If neither of the above is specified, the default is:
    • on Unix systems, $HOME/.config/mihomo.
    • on Windows, %USERPROFILE%/.config/mihomo.

BUG & Fix

Maintenance

Full Changelog: v1.19.8...v1.19.9

Contributors

wwqgtxx
Loading

v1.19.8

13 May 04:28
@github-actions github-actions
v1.19.8
266fb03

Choose a tag to compare

View all tags
v1.19.8

What's Changed

  • For security reasons, the "path" parameter of /configs in the restful api has been restricted, and its directory also needs to be in workdir or SAFE_PATHS.
  • Other incompatible updates are the same as v1.19.6:
  • For security reasons, all paths appearing in the configuration file will be limited to workdir (regardless of whether they are relative or absolute). If there is a specific need, please specify additional safe paths by setting the SAFE_PATHS environment variable while ensuring safety. The syntax of this environment variable is the same as the PATH environment variable parsing rules of this operating system (i.e., semicolon-separated under Windows and colon-separated under other systems)
  • In addition, support for specifying routing-mark and interface-name for proxy-groups has been removed. Please specify the relevant parameters in proxies directly.
  • Note: The workdir mentioned above is specified by the -d parameter when the program is started or the CLASH_HOME_DIR environment variable. If neither of the above is specified, the default is:
    • on Unix systems, $HOME/.config/mihomo.
    • on Windows, %USERPROFILE%/.config/mihomo.

BUG & Fix

Maintenance

  • 2116640 chore: the updateConfigs api also adds a check for SAFE_PATHS by @wwqgtxx
  • 23e2d3a chore: rebuild provider load by @wwqgtxx
  • 266fb03 chore: update dependencies by @wwqgtxx
  • 76e9607 chore: move start healthcheck.process() from New to Initial in provider avoid panic cause by build-in proxy have not set to tunnel by @wwqgtxx

Full Changelog: v1.19.7...v1.19.8

Contributors

wwqgtxx
Loading

v1.19.7

12 May 02:09
@github-actions github-actions
v1.19.7
a4fcd3a

Choose a tag to compare

View all tags
v1.19.7

What's Changed

  • The incompatible updates of the restful api not mentioned in the previous version of the changelog have been rolled back, solving the problem that the related gui cannot refresh the configuration
  • Note that for security reasons, we are currently planning to restrict the "path" parameter of /configs in restful api in the next version, and its directory also needs to be in SAFE_PATHS or workdir. It is recommended that downstream clients adapt to this change in advance. (This change has been applied to alpha version 2116640)
  • Other incompatible updates are the same as v1.19.6:
  • For security reasons, all paths appearing in the configuration file will be limited to workdir (regardless of whether they are relative or absolute). If there is a specific need, please specify additional safe paths by setting the SAFE_PATHS environment variable while ensuring safety. The syntax of this environment variable is the same as the PATH environment variable parsing rules of this operating system (i.e., semicolon-separated under Windows and colon-separated under other systems)
  • In addition, support for specifying routing-mark and interface-name for proxy-groups has been removed. Please specify the relevant parameters in proxies directly.

BUG & Fix

  • d22a893 fix: hysteria server port hopping compatibility issues by @wwqgtxx

Maintenance

Full Changelog: v1.19.6...v1.19.7

Contributors

wwqgtxx and muink
Loading