Skip to content

Dupli-Annihilator-G v2.9.9

Choose a tag to compare

@bultodepapas bultodepapas released this 13 Mar 19:27
· 6 commits to main since this release

Dupli-Annihilator-G v2.9.9

Executive Summary

v2.9.9 is the clean follow-up release that packages the desktop and CLI artifacts from a fully consistent tagged state.

It carries forward the dedupe engine improvements introduced in v2.9.7 and the desktop NSIS packaging fix prepared after that release, while also fixing the release workflow so the desktop Cargo.lock is regenerated and committed as part of version preparation.


Fix: Release Consistency For Desktop Builds

What changed

  • the release preparation script now regenerates apps/desktop/src-tauri/Cargo.lock,
  • the same script now stages apps/desktop/src-tauri/Cargo.lock into the release commit,
  • desktop packaging remains aligned with the valid NSIS install mode currentUser.

Why it matters

This ensures the published desktop assets come from the exact tagged source state instead of a post-tag lockfile refresh.


Included Assets In This Manual Release

This GitHub Release is published manually and includes ready-to-download Windows assets built from tag v2.9.9:

  • Dupli-Annihilator-G_2.9.9_x64-setup.exe
  • dedupe_desktop_tauri.exe
  • dedupe_cli.exe
  • SHA256SUMS.txt

Distribution Note

This release still does not include signed updater artifacts because the GitHub Actions signing credentials are not configured in this repository environment.

Included:

  • source code for tag v2.9.9,
  • release notes,
  • unsigned Windows desktop installer,
  • unsigned Windows desktop executable,
  • Windows CLI executable,
  • SHA-256 checksums for the attached binaries.

Not included:

  • signed desktop installers,
  • CI-published updater metadata,
  • notarized macOS artifacts,
  • signed Linux updater artifacts.

Validation

  • node scripts/release/prepare-release.mjs 2.9.9 --commit --tag --push
  • cargo build -p dedupe_cli --release
  • cargo tauri build --ci --no-sign

Compatibility

  • No breaking API changes.
  • No dedupe output format changes.
  • Existing engine semantics are preserved.