{"version":"2.1.257","anchor":"new-telemetry-event-distinguishing-skipped-unverified-relea","canonical_anchor":"native-installer-verifies-staged-binary-checksum-before-acti","heading":"Native updater verifies staged binary checksum and skips unverified releases, with new telemetry","tier":"notice","area":"Updater","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/new-telemetry-event-distinguishing-skipped-unverified-relea","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Native updater verifies staged binary checksum and skips unverified releases, with new telemetry\n\nAuto-update telemetry now reports a release skipped for failing verification as its own outcome.\n\nThe native installer now throws a new error class if a staged binary's checksum no longer matches what was verified, blocking install\/update instead of silently activating an unverified binary. Related logic also skips activating releases that predate release-signature enforcement, recorded as `skippedUnverifiedRelease`.\n\nTelemetry event selection for the native auto-updater was refactored into a helper that returns `tengu_native_auto_updater_success`, a new `tengu_native_auto_updater_skipped_unverified_release`, or `tengu_native_auto_updater_up_to_date`, based on the `wasUpdated`\/`skippedUnverifiedRelease` flags on the result.\n\n- Area: Updater\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}