Update barcalendar.py to reflect current openedx-supported versions - #730
Open
UsamaSadiq wants to merge 1 commit into
Open
Update barcalendar.py to reflect current openedx-supported versions#730UsamaSadiq wants to merge 1 commit into
UsamaSadiq wants to merge 1 commit into
Conversation
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
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.
Description
Closes #729.
Verified every hardcoded version and EOL date in
barcalendar.pyagainst the actual dependencies used by the current Open edX release (release/ulmo.3, tutor v21.0.8) and against each section's cited authoritative source (endoflife.date, elastic.co, djangoproject.com, nodejs Release schedule).Changes:
Python (3.11) and Django (5.2) were checked and found to already be correct against the ulmo.3 release branch, no change needed there.
Testing
Ran
barcalendar.pybefore and after the change. After the fix, the only remaining validation warnings are expected ones: future Django/Ubuntu releases not yet published on endoflife.date, and Elasticsearch entries that intentionally follow elastic.co's official major-version support policy rather than endoflife.date's per-minor-version tracking (documented in the code).