Isolate optional desktop shortcut failures
This commit is contained in:
@@ -1,6 +1,19 @@
|
||||
|
||||
# Changelog
|
||||
|
||||
## [2.2.4] - 2026-08-24
|
||||
### Fixed
|
||||
- Permission, Windows Script Host, validation and rollback errors affecting the optional all-users desktop shortcut no longer abort installation, update or uninstallation.
|
||||
- Failure to capture or restore the optional desktop shortcut can no longer prevent restoration of mandatory registry, Start menu and uninstaller state.
|
||||
|
||||
### Changed
|
||||
- The all-users desktop shortcut is now opt-in and unchecked by default.
|
||||
- Optional desktop warnings are visible in the setup UI and durable log, while completion remains successful with an explicit warning result.
|
||||
|
||||
### Added
|
||||
- Failure-injection coverage proving that both an optional shortcut exception and a failing warning sink remain non-fatal.
|
||||
- Dedicated operator and maintainer documentation for the optional Windows-integration boundary.
|
||||
|
||||
## [2.2.3] - 2026-08-24
|
||||
### Fixed
|
||||
- A persistent Windows/EDR denial of the final staging-directory rename no longer aborts activation after an existing installation has already been atomically moved to its backup.
|
||||
|
||||
Reference in New Issue
Block a user