Fix typo'd last_update_date in biomeSync (2029 -> 2025)#1688
Merged
Conversation
biomeSync.py had last_update_date '2029-09-29' (a future date). Git shows the value was written in commit b67c38a on 2025-09-29, so the intended year was 2025. creation_date is 2023-03-22, confirming 2029 is a typo.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
biomeSync.py("Biome - Device Syncs") haslast_update_date: '2029-09-29'— a future date. Git history shows the value was set in commit b67c38a ("Update last_update_date in appConduit.py and biomeSync.py") authored 2025-09-29, andcreation_dateis2023-03-22, so the intended year is 2025. One-character metadata fix, no logic change.Spotted while surfacing
last_update_dateon the leapps.org artifact browser.