Move the agent and tray to 1.20.1 and 1.7.1
No behaviour change. The 1.20.0 and 1.7.0 binaries were built and shipped to the display scope before two fixes landed - the fast retry while an enrollment is pending, and the fleet alert key rename - so a rebuild carried different bytes under the same version number. Detection is by hash and copes with that, but nobody reading a version number can tell two 1.20.0.0 files apart, and the runbook asks for one build across the share, the agent store and the display profile. The version moves instead.
This commit is contained in:
@@ -116,8 +116,14 @@
|
|||||||
balloon, and alert polling logs at a throttled rate and retries. An alert
|
balloon, and alert polling logs at a throttled rate and retries. An alert
|
||||||
is recorded as acknowledged only when the agent confirms it, so a failed
|
is recorded as acknowledged only when the agent confirms it, so a failed
|
||||||
ack lets it reappear. The collect-usercontext probe is unchanged.
|
ack lets it reappear. The collect-usercontext probe is unchanged.
|
||||||
Requires the agent release that hosts the pipe. -->
|
Requires the agent release that hosts the pipe.
|
||||||
<Version>1.7.0</Version>
|
|
||||||
|
1.7.1: no behaviour of its own. The fleet alert key rename landed
|
||||||
|
after the 1.7.0 binary was built and shipped to the display scope,
|
||||||
|
so the rebuild carries different bytes under the same version. The
|
||||||
|
version moves so the two can be told apart. Pairs with agent
|
||||||
|
1.20.1. -->
|
||||||
|
<Version>1.7.1</Version>
|
||||||
<InvariantGlobalization>true</InvariantGlobalization>
|
<InvariantGlobalization>true</InvariantGlobalization>
|
||||||
<RuntimeIdentifier>win-x64</RuntimeIdentifier>
|
<RuntimeIdentifier>win-x64</RuntimeIdentifier>
|
||||||
<SelfContained>true</SelfContained>
|
<SelfContained>true</SelfContained>
|
||||||
|
|||||||
@@ -286,8 +286,16 @@
|
|||||||
caller's own profile. appsettings.json is restricted to SYSTEM and
|
caller's own profile. appsettings.json is restricted to SYSTEM and
|
||||||
Administrators once the pipe is up. The 1.19 client-certificate renewal
|
Administrators once the pipe is up. The 1.19 client-certificate renewal
|
||||||
and expiry monitor are removed, and with them the non-zero exit at start.
|
and expiry monitor are removed, and with them the non-zero exit at start.
|
||||||
Pairs with tray 1.7.0. -->
|
Pairs with tray 1.7.0.
|
||||||
<Version>1.20.0</Version>
|
|
||||||
|
1.20.1: no behaviour of its own. Two fixes landed after the 1.20.0
|
||||||
|
binaries had already been built and shipped to the display scope -
|
||||||
|
the fast retry while an enrollment is pending, and the fleet alert
|
||||||
|
key rename - so the rebuild carries different bytes under the same
|
||||||
|
version. Detection is by hash and copes, but two files calling
|
||||||
|
themselves 1.20.0.0 cannot be told apart by anyone reading a
|
||||||
|
version number, so the version moves. Pairs with tray 1.7.1. -->
|
||||||
|
<Version>1.20.1</Version>
|
||||||
<InvariantGlobalization>true</InvariantGlobalization>
|
<InvariantGlobalization>true</InvariantGlobalization>
|
||||||
<RuntimeIdentifier>win-x64</RuntimeIdentifier>
|
<RuntimeIdentifier>win-x64</RuntimeIdentifier>
|
||||||
<SelfContained>true</SelfContained>
|
<SelfContained>true</SelfContained>
|
||||||
|
|||||||
Reference in New Issue
Block a user