Skip to content

fix: skip self-update when binary already matches latest asset#9

Merged
thomasjiangcy merged 2 commits intomainfrom
fix/self-update-binary-match-noop
Feb 24, 2026
Merged

fix: skip self-update when binary already matches latest asset#9
thomasjiangcy merged 2 commits intomainfrom
fix/self-update-binary-match-noop

Conversation

@thomasjiangcy
Copy link
Copy Markdown
Owner

Summary

  • avoid unnecessary executable replacement in pkgrep self update
  • after downloading and extracting the latest release asset, compare it against the current installed binary
  • if bytes match, exit as no-op with clear status message
  • add checksum parser test coverage for *filename checksum format tokens
  • add changelog note under Unreleased

Why

Current binary version strings can lag release tags in some workflows. This follow-up prevents repeated self-update rewrites when the installed binary already matches the latest release artifact.

Validation

  • cargo test --all-targets --all-features
  • cargo clippy --all-targets --all-features -- -D warnings
  • ./.dev/check_no_mocks.sh

@thomasjiangcy thomasjiangcy merged commit 96c22f1 into main Feb 24, 2026
3 checks passed
@thomasjiangcy thomasjiangcy deleted the fix/self-update-binary-match-noop branch February 24, 2026 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant