Cursor can republish the same semver with a new build; the updater
previously skipped prefetch when the version matched, leaving stale
sha256 values. In CI, always re-prefetch and commit when flake.nix drifts.
- Added CURSOR_VERSION_INFO output to track update status in update-cursor.sh
- Implemented auto-confirmation for updates when running in CI mode
- Updated GitHub Actions workflow to capture and utilize CURSOR_VERSION_INFO for conditional commits
- Improved commit message generation based on actual version updates
- Added 'Update flake lock file' step that runs 'nix flake update'
- Modified commit step to include both flake.nix and flake.lock files
- Ensures lock file stays in sync when flake is updated
- Added permissions for write access to contents
- Simplified update process by integrating update-cursor.sh script
- Removed redundant steps for fetching and checking versions
- Enhanced commit logic to only push changes if there are updates