Feature: Auto-update client

[mohamed-essam]

Describe your changes

Issue ticket number and link

Stack

Checklist

• Is it a bug fix
• Is a typo/documentation fix
• Is a feature enhancement
• It is a refactor
• Created tests that fail without the change (if possible)
• Extended the README / documentation, if necessary
• Documentation is not needed

By submitting this pull request, you confirm that you have read and agree to the terms of the Contributor License Agreement.

[robertgro]

Related

#1793

#4019

[mohamed-essam]

@lixmal All comments should be resolved, will need to conduct another round of testing however, so will keep the PR as Draft until testing is complete

[Copilot]

Pull Request Overview

This PR introduces an auto-update client feature that allows the management server to control client version updates. The feature enables administrators to specify a target version for clients, which can be "latest", "disabled", or a specific semantic version.

• Added AutoUpdateVersion field to account settings with validation for "latest", "disabled", or semantic version format
• Implemented platform-specific update mechanisms for Windows, macOS, Linux, and FreeBSD
• Added update manager that monitors version changes and triggers updates when client version is older than target

Reviewed Changes

Copilot reviewed 19 out of 19 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
version/update.go	Made LatestAvailable field public for external access
management/server/types/settings.go	Added AutoUpdateVersion field to Settings struct
management/server/token_mgr.go	Added AutoUpdateVersion to TURN/relay token updates
management/server/peer.go	Added AutoUpdateVersion to peer deletion updates
management/server/http/handlers/accounts/	Added API handlers and validation for AutoUpdateVersion
management/server/http/api/	Added AutoUpdateVersion to API types and OpenAPI spec
management/server/grpcserver.go	Added AutoUpdateVersion to sync response
management/server/activity/codes.go	Added activity tracking for AutoUpdateVersion updates
management/server/account.go	Added handling for AutoUpdateVersion setting changes
management/proto/management.proto	Added autoUpdateVersion field to SyncResponse
client/internal/updatemanager/	Implemented platform-specific update mechanisms
client/internal/engine.go	Integrated update manager with sync response handling

[lixmal]

Have you put any thoughts into how we could do a rollback if the new version breaks connectivity?

[mohamed-essam]

@lixmal

Have you put any thoughts into how we could do a rollback if the new version breaks connectivity?

Based on my discussions with @mlsmaycon , the upgrade mechanism is forward-moving only

[mohamed-essam]

@lixmal If it's alright with you, I will mark the PR as no documentation needed for the time being as the dashboard changes are not yet done, as soon as dashboard can modify the auto upgrade version I will open a PR in docs

[pascal-fischer]

Why do we have to send this even on messages that should not care about this? The absence of the string should indicate that we do not handle it. There is no need to send a skip string. AutoUpdateVersion should be optional then

[mohamed-essam]

It was agreed with @mlsmaycon that empty == latest, this is why

[pascal-fischer]

@mlsmaycon Why???

[Tristan-Theroux]

Hey,

Just wondering when is this expected to be released in production ?

Best,

[yshah-aromatech]

Hi Team,

Do we have an expected date for this release?

Thanks

[wgetnz]

Do we have an expected date for this release?

[BashBandito]

Very much looking forward to this feature.

Thanks for the good work.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud