Release QA: `fleetd` update

[lukeheath]

fleetd agent:

Includes updates to:

• Orbit: True
• Desktop: True
• Chrome extension: True

List versions changes for any component updates below:

• Orbit v1.24.0 > v1.25.0
• Desktop v1.24.0 > v1.25.0
• Chrome extension v1.3.0 > v1.3.1

Prerequisites

1. Build a new fleetd from the release candidate branch as neded for Orbit, Desktop, and Chrome Extension.

Test name	Step instructions	Expected result	pass/fail
$Name	{what a tester should do}	{what a tester should see when they do that}	pass/fail
`fleetd` tests	1. Create binaries for Mac, Windows, and Ubuntu running against the `edge` channels and install (--orbit-channel edge, --desktop-channel edge). 2. Work with engineer leading the release to push changes to the `edge` channel.	1. Confirm the hosts running on the edge channel receive the update and are working correctly. 2. Confirm any new features and/or bug fixes associated with this release are working as intended.	pass/fail
`fleetd` auto-update tests	1. Conduct the [`fleetd` auto-update n+1 test]([url](https://github.com/fleetdm/fleet/blob/main/tools/tuf/test/Fleetd-auto-update-test-guide.md)) 2. QA certifies new release by commenting in issue. 3. Engineer waits at least 1 business day, then promotes update to `stable`.	1. Agent successfully auto-updates. 2. Issue is certified by QA. 3. Agent is promoted to `stable`. 4. Confirms agents running on `stable` receive the new update.	pass/fail

Notes

Issues found new to this version:

Issues found that reproduce in last stable version:

What has not been tested:

Include any notes on whether issues should block release or not as needed:

[lukeheath]

@sharon-fdm @georgekarrv As part of my freeze ritual, I saw that changes to orbit need to be published with this release. It looks like one change is endpoints ops, and the other is MDM, so you will need to coordinate who is going to handle publishing this release (presumably either Lucas or Roberto).

[sharon-fdm]

@lukeheath @georgekarrv Yeh, either teams can take it. I don't mind taking it if MDM is busy.

cc: @lucasmrod

[lukeheath]

@sharon-fdm Sounds good! We'll want to make sure the MDM change gets QA'd as part of release testing.

[sharon-fdm]

@lucasmrod I'm assigning you as release owner. Please work with @xpkoala and @PezHub to validate the two fixes. @lukeheath, Lucas has 5 points in progress (including the P2). Is it ok that this should start later this week or early next one?

[lukeheath]

@sharon-fdm Yes, early next week is good.

[sharon-fdm]

Est 1 pt for @lucasmrod

[lucasmrod]

@lukeheath For fleetd-chrome we now have a changes/ folder (that's how we can determine if a fleetd-chrome release is needed):

ls ee/fleetd-chrome/changes/

[lukeheath]

@getvictor I've added the Chrome extension update to this ticket for tracking.

[fleet-release]

Orbit, Desktop, Chrome, Updated, secure and safe home. Fleet's strength in each dome.

Versions rise like sun, New dawn for our fleet begun, Cloud city's work done.

Tests pass, stable waits, In the cloud city's high gates, Fleet's update resonates.