NewYour coding agent can read the release notes before it upgrades.Set up the MCP server β
Go modules, #306 by repository stars
Latest stable
v1.8.0
Last release 4 days ago
18 Nov 2026
Ships on a steady schedule
a new release about every 2 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
924 releases Β· first in 2021
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Netmaker v1.8.0 Release Notes π
Completely redesigned Netmaker Desktop Apps for a faster, stable connection experience.
auto_select_exit_node), desktop/user devices are automatically assigned an allowed internet exit (nearest available) when they connect; users can still switch exits when permitted.Secure, managed SSH access to hosts through Netmaker β without opening inbound SSH on the public internet.
Updated network map experience for clearer topology and device context.
Windows hosts can now act as egress gateways.
New option on internet egress so traffic to other (site) egress destinations does not hairpin through the internet exit.
bypass_egress_routes (internet egress only) β enable to avoid that hairpin for other egress sites; disable to force site-egress traffic via the internet exit.Connect an identity provider once at the organisation level and automatically provision org users.
Create long-lived API keys for automation and integrations, instead of using user session tokens.
/api/v1/api-keys; send the key as a Bearer token (nm_live_β¦). Actions are audit-logged as API Key: <name>.This release runs migration-v1.8.0, which continues the SQL schema path after multi-tenancy (org/tenant) from v1.7.0. It migrates remaining key-value resources into versioned tables, backfills IP pools/allocations, and applies internet-egress defaults.
What migration-v1.8.0 does:
*_v1 schema tables (network resolved by name within tenant).owner_username values on hosts (re-established by current device ownership flows).Also on startup (idempotent helpers):
IsInternetGateway) into internet-type egress resources and exit-node selections.network_global_access on default network-admin roles.Upgrade requirement (existing deployments):
migration-v1.7.0 has not completed on a prior v1.7.0 deployment.Pre-upgrade check (IP uniqueness):
migration-v1.8.0 will fail until duplicates are resolved.Impact:
π Action Required:
migration-v1.7.0 completed on v1.7.0 before moving to v1.8.0.For detailed upgrade steps, refer to the official upgrade documentation:
Migration reliability β v1.8.0 blocks startup until migration-v1.7.0 completed on existing deployments; IP pool backfill fails clearly on duplicate addresses instead of corrupting allocations.
IP address management β Networks gain managed IP pools/allocations; pools are synced on startup so existing networks can allocate addresses safely.
Auto-relay performance β Lower CPU use for auto-relay; API to list auto-relayed peers for a node; reset a specific auto-relayed peer pair without resetting the whole network.
User-device / desktop ACL paths β CE supports user ACL policies with All Users and per-user sources; AllowAll is preserved when both default policies are open; FwUpdate calc skipped for user-owned devices where appropriate.
Exit node + relay β Selecting an exit node can replace an existing relay; alternate exit peers limited to user devices (servers continue to hairpin via the selected exit).
Host / device auth β Reject host-password JWTs for user-owned devices; AuthorizeHost accepts a user session plus X-Host-ID. Network-role API access tightened for network admins.
Extclient reliability β Bulk create API and faster creation; mark extclients offline when their ingress gateway is unreachable; keep static WireGuard configs across JIT, IdP, and access cleanup paths.
Topology / map data β Topology and connections enriched with location, gateway flags, and egress context.
Device join resilience β Device join/pull tolerates host.Nodes drift vs live nodes.
Account lifecycle β Force logout and user-device cleanup when disabling/deleting user accounts; username filter on nodes API.
Email usernames β Email-style usernames normalized to lowercase (invites and migration).
Traffic keys β AES key derivation via ECDH; stronger validation of traffic public keys.
IPv6-only machines
Netclients cannot currently auto-upgrade on IPv6-only systems.
Multi-network join performance
Multi-network netclient joins using an enrollment key still require optimization.
systemd-resolved DNS limitation
On systems using systemd-resolved in uplink mode, only the first 3 entries in resolv.conf are honored; additional entries are ignored. This may cause DNS resolution issues. Stub mode is recommended.
Windows Desktop App + mixed gateway modes
When the Windows Desktop App is connected to both:
the gateway monitoring component may disconnect from the Split Tunnel Gateway.
Duplicate overlay IPs block v1.8.0 migration
Networks with the same address on multiple nodes/extclients must be cleaned up before migration-v1.8.0 can complete.
Your coding agent can read these notes before it upgrades. Set up the MCP server β
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Netmaker v1.7.0 Release Notes π
Run multiple customer environments from a single Netmaker server.
nmctl select the target org/tenant via X-Organization-ID / X-Tenant-ID (--org_id / --tenant_id), with nmctl organisation list and nmctl tenant list for discovery.Gateways can publish a TCP/WSS uplink so clients can reach the mesh in restrictive environments when UDP is blocked.
tcp_proxy_enabled and related listen/TLS settings).Connect endpoint detection and response platforms for posture checks from Integrations.
/api/v1/integrations/edr/{provider}).Connect mobile device management platforms for device compliance posture from Integrations.
/api/v1/integrations/mdm/{provider}).This release completes the SQL schema path and introduces multi-tenancy (org/tenant) bootstrap as part of the v1.7.0 migration.
Upgrade requirement (existing deployments):
migration-v1.6.0 has not completed on a prior v1.6.0 deployment.Impact:
π Action Required:
For detailed upgrade steps, refer to the official upgrade documentation:
Auto-relay peer reset - Reset a specific peer-to-peer connection that is using a relay (clear/reassign auto-relay for that peer pair) without resetting the entire networkβs auto-relay state.
Host status - Host filtering uses live check-in status (Online/Offline/Disconnected) rather than a stale DB value.
MSP installs - nm-quick.sh -s flag to skip nmctl/mesh/netclient on MSP server installs.
IPv6-only machines
Netclients cannot currently auto-upgrade on IPv6-only systems.
Multi-network join performance
Multi-network netclient joins using an enrollment key still require optimisation.
systemd-resolved DNS limitation
On systems using systemd-resolved in uplink mode, only the first 3 entries in resolv.conf are honoured; additional entries are ignored. This may cause DNS resolution issues. Stub mode is recommended.
Windows Desktop App + mixed gateway modes
When the Windows Desktop App is connected to both:
the gateway monitoring component may disconnect from the Split Tunnel Gateway.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Netmaker v1.6.0 Release Notes π
Using Netmaker's Egress function at local sites, paired with local routing rules, you can bridge entire networks (site-to-site). Now, Netmaker allows you to define ACL policies that control what traffic is allowed between these sites.
Netmaker's Egress function forwards traffic to external networks like offices and data centres. Netmaker's Access Controls can now target individual IPs inside of an egress range using the ip ACL target type. This enables you to limit access to specific IPs within an external network.
Simplified application-aware egress routing with a built-in catalogue of popular SaaS and cloud services.
Just-In-Time (JIT) access is a workflow within Netmaker where users request temporary access to the network, which is approved by administrators for a predefined time period. JIT access within Netmaker can now be scoped to user groups per network.
Netmaker provides audit logs of actions and events on the platform. Netmaker can now be integrated with certain providers to forward audit events to your security stack.
Enrollment keys are how devices join the network via Netclient. Administrators can now designate a default enrollment key for any network in order to simplify device onboarding.
This release introduces schema changes to the following core entities:
Impact:
π Action Required:
For detailed upgrade steps, refer to the official upgrade documentation:
Netclient registration UX β Host registration over OAuth/basic auth now returns clear websocket close reasons on failure (auth errors, missing access, posture violations, and server errors).
User group management β Streamlined user role permissions and group updates, role-downgrade handling.
Orphan reference cleanup β Removes stale network references left behind after resource deletion.
Scalability & reliability β Optimised node status calculation, offline-status hooks, zombie/orphan node cleanup, and ACL cache race fixes.
API hardening β Auth rate limiting on REST endpoints and activity-log permission fixes.
Egress improvements β CIDR validation for ACL egress IPs, multi-domain egress routing, and domain-answer handling for preset-based egress.
Failover removed β Legacy per-node failover APIs and CLI commands have been removed in favour of gateway-based patterns.
IPv6-only machines
Netclients cannot currently auto-upgrade on IPv6-only systems.
Multi-network join performance
Multi-network netclient joins using an enrollment key still require optimisation.
systemd-resolved DNS limitation
On systems using systemd-resolved in uplink mode, only the first 3 entries in resolv.conf are honoured; additional entries are ignored. This may cause DNS resolution issues. Stub mode is recommended.
Windows Desktop App + mixed gateway modes
When the Windows Desktop App is connected to both:
The gateway monitoring component may disconnect from the Split Tunnel Gateway.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.