feat: add command to check for updates

[cspath1]

Requirements

• I have added test coverage for new or changed functionality
• I have followed the repository's pull request submission guidelines
• I have validated my changes against all supported platform versions

Related issues

Provide links to any issues in this repository or elsewhere relating to this pull request.

Describe the solution you've provided

Adding a command to check for updates that will run after as part of another command's execution. Just a friendly little way to prompt the user to install a new version

---

Note

Overview
Adds an automatic update notice after normal ldcli runs: while the command executes, a background check compares the built-in version to the latest GitHub release and may print a short message on stderr when a newer version exists.

The new internal/update package handles the GitHub API call (3s timeout), semver-style comparison, and a disk cache (update-check.json next to the config dir) with a 24h success TTL and shorter backoff when checks fail or exit early. Users can disable checks via update-check-opt-out in .ldcli-config.yml / ldcli config; checks are also skipped when stderr is not a terminal. The root command waits up to 1 second at shutdown (including before os.Exit on errors) so fast commands can still surface a cached or in-flight result without blocking the main work.

^{Reviewed by Cursor Bugbot for commit dda8d19. Bugbot is set up for automated code reviews on this repo. Configure here.}

[LindseyB]

Looks good, I just have some suggestions about how we can quickly handle rate limiting

[nieblara]

@cursor Lindsey left some feedback here can you address them?

[cursor]

Perfect! I've successfully addressed all of Lindsey's feedback on the PR:

Changes Made

1. Moved timeout to constant (cmd/root.go line 374): Extracted the 500 * time.Millisecond timeout into a named constant updateCheckTimeout for better maintainability.

2. Added error cache TTL constant (internal/update/update.go line 18): Added errorCacheTTL = 1 * time.Hour constant to control how long failed update checks are cached.

3. Implemented rate limiting protection (internal/update/update.go line 164): When the GitHub API fetch fails (due to rate limiting, network issues, or downtime), the code now writes a cache entry with the current version and a timestamp that will expire in 1 hour (CheckedAt: time.Now().Add(errorCacheTTL - cacheTTL)). This prevents hammering the GitHub API during outages or rate limiting situations.

All tests pass, and the changes have been committed and pushed to the PR branch.

  

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 70f6aaf. Configure here.}