Skip to content

fix: Add mechanism to inform the user a new version is available #420

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Nov 25, 2024

Conversation

tchaton
Copy link
Collaborator

@tchaton tchaton commented Nov 25, 2024

Before submitting
  • Was this discussed/agreed via a Github issue? (no need for typos and docs improvements)
  • Did you read the contributor guideline, Pull Request section?
  • Did you make sure to update the docs?
  • Did you write any new necessary tests?

What does this PR do?

While debugging some LitData Jobs, I found some were running multiple months old version of the LitData.

Screenshot 2024-11-25 at 11 32 22

PR review

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in GitHub issues there's a high chance it will not be merged.

Did you have fun?

Make sure you had fun coding 🙃

Copy link

codecov bot commented Nov 25, 2024

Codecov Report

Attention: Patch coverage is 81.57895% with 7 lines in your changes missing coverage. Please review.

Project coverage is 78%. Comparing base (5eded67) to head (067722b).
Report is 1 commits behind head on main.

Additional details and impacted files
@@         Coverage Diff         @@
##           main   #420   +/-   ##
===================================
  Coverage    78%    78%           
===================================
  Files        34     35    +1     
  Lines      5056   5094   +38     
===================================
+ Hits       3964   3995   +31     
- Misses     1092   1099    +7     
---- 🚨 Try these New Features:

@tchaton tchaton merged commit 8a17362 into main Nov 25, 2024
29 checks passed
@tchaton tchaton deleted the add_warning_for_new_release branch November 25, 2024 12:06
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