What changed in frp, release by release
The lines under each release are frp's own release-note bullets with pull request numbers, names and links removed, grouped by its own headings. Wording is theirs. Not affiliated with frp.
v0.72.0
- NewFrpc can verify server certificates using system CAs, optionally combined with CAs from trustedCaFile.
- NewFrpc reload now refreshes certificate files for unchanged https2http and https2https proxies without interrupting existing connections. Failed…
- FixedFixed proxy and visitor configuration changes being lost when reloading frpc during reconnection.
- FixedUpdated yamux to fix a 100% CPU busy loop after a session shuts down and a session close that could hang when the underlying connection (for example…
v0.71.1
- NewBuilding frp from source now requires Go 1.26.0 or later.
- FixedUpdated dependencies to fix SSH tunnel gateway channel deadlocks and panics caused by malformed challenges from NTLM-authenticated HTTP proxies.
- FixedFixed VirtualNet routing issues during reconnection and shutdown, and excessive retries after repeated connection failures.
v0.71.0
- NewUDP packet payloads for ordinary UDP proxies and SUDP now use a dedicated binary codec when frpc and frps successfully negotiate the capability under…
- FixedFixed a server panic and remote denial of service caused by a client sending a negative
pool_count. Negative values are now rejected before… - FixedFixed frpc verify ignoring configured featureGates, which caused VirtualNet configurations to be rejected even when the feature was enabled.
v0.70.1
- FixedHTTP vhost servers no longer support HTTP/1.1 Upgrade: h2c requests. Cleartext HTTP/2 prior-knowledge remains supported.
- FixedFixed control-session replacement leaks when frpc reconnects through a half-open TCP multiplexed connection.
v0.70.0
- NewExpanded the frps dashboard API v2 migration across Clients, Proxies, Server Overview, Client Detail, and Proxy Detail, covering paginated…
- FixedWebSocket and WSS tunnel payloads are now sent as binary frames, avoiding disconnects through RFC-compliant intermediaries that validate text frames…
- FixedThe tls2raw client plugin now writes the proxy protocol header to the local raw connection when proxy protocol is enabled.
v0.69.1
- NewTransport.wireProtocol = "v2" now also applies to UDP-based proxy payloads, including ordinary UDP and SUDP, so their payload framing is consistent…
- NewImproved SUDP compatibility during mixed transport.wireProtocol deployments, allowing frps to bridge payloads between v1/default and v2 SUDP clients.
- ChangedWhen enabling transport.wireProtocol = "v2" for SUDP, upgrade both the proxy and visitor frpc instances first, or keep them on v1 until both sides…
v0.69.0
- NewAdded transport.wireProtocol for frpc to select the internal message protocol used between frpc and frps. Supported values are v1 and v2.
- NewAdded client protocol visibility in the frps dashboard and /api/clients API. Online clients now report their negotiated protocol as v1 or v2.
v0.68.1
- FixedFixed a configuration-dependent authentication bypass in type = "http" proxies when routeByHTTPUser is used together with httpUser / httpPassword.…
v0.68.0
- NewAdded a built-in store capability for frpc, including persisted store source ([store] path = "..."), Store CRUD admin APIs (/api/store/proxies*,…
- NewKept proxy/visitor names as raw config names during completion; moved user-prefix handling to explicit wire-level naming logic.
v0.67.0
- NewFrpc now supports a clientID option to uniquely identify client instances. The server dashboard displays all connected clients with their…
- NewRedesigned the frp web dashboard with a modern UI, dark mode support, and improved navigation.
- FixedFixed UDP proxy protocol sending header on every packet instead of only the first packet of each session.
How we calculate
- Days between releases: The median of the gaps, in days, between the release dates listed above.
Data: fatedier/frp's GitHub releases page, read November 18, 2026. Every other figure on this page is copied from the record, not calculated by us.
Get this for your repo, every release
frp publishes release notes that people can read. FoxPlug writes yours from what you ship: a changelog entry and posts for the places your users are, each approved by you.
Get this for your repo, every releaseTry it on your repo nowYour changelog, written for you
FoxPlug writes your changelog from your releases and commits in plain English and publishes it as a page and a feed your users can follow. The page above shows what that looks like for a product people really use.
Write my changelog See the changelog FoxPlug wrote from its own commits
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Written from your releases and commits, in plain English your users read
- Connect GitHub and new releases become new entries