Check for update, ask user to update, auto update

[mahbd]

PR Type

Feature

PR Checklist

• Tests for the changes have been added / updated.
• Documentation comments have been added / updated.
• A changelog entry has been made.
• Version number has been updated.
• Required modules have been added to respective "requirements*.txt" files.
• Relevant Test Cases added to this description (below).
• (Team) Label with affected action categories and semver status.

Overview

This PR introduces a self-updating mechanism for the ZeuZ Node, allowing users to stay current with releases without manual intervention.

Changes:

• update.go Implementation: Introduced a dedicated module to handle version comparison, update fetching from the GitHub API, and file replacement logic.
• Makefile Updates: Integrated update.go into the build process across all supported platforms (Windows, macOS, Linux) to ensure the update binary is bundled with every release.
• Logic Improvements:
  • Added an asynchronous update check on startup to minimize latency.
  • Implemented a user-friendly CLI prompt providing options to update now, postpone, ignore the current version, or enable auto-updates.
  • Enhanced main.go file download logic to support cross-device renaming on Windows by falling back to a file-copy mechanism if os.Rename fails.
  • Added state persistence via update_prefs.json and update_cache.json in the .zeuz directory to track user preferences and cached release metadata.

Why:
To improve the user experience and ensure nodes are running the latest version, reducing the friction associated with manual binary replacement and minimizing potential compatibility issues with outdated software.

Test Cases

• TEST-0000

[mahbd]

📚 $\text{Stack Overview}$

Pulls submitted in this stack:

• Check for update, ask user to update, auto update #684 👈
• dev

This comment was automatically generated by st.