List versions changes for any component updates below:
Orbit v1.34.0 > v1.35.0
Desktop v1.34.0 > v1.35.0
Prerequisites
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:
fleetd
agent: Publish before Fleet v4.59.0Includes updates to:
List versions changes for any component updates below:
v1.34.0
>v1.35.0
v1.34.0
>v1.35.0
Prerequisites
fleetd
from the release candidate branch as neded for Orbit, Desktop, and Chrome Extension.2. Work with engineer leading the release to push changes to the `edge` channel.
2. Confirm any new features and/or bug fixes associated with this release are working as intended.
2. QA certifies new release by commenting in issue.
3. Engineer waits at least 1 business day, then promotes update to `stable`.
2. Issue is certified by QA.
3. Agent is promoted to `stable`.
4. Confirms agents running on `stable` receive the new update.
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: