Skip to content
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

chore!: upgrade Django version to 4.2 (LTS) #34113

Merged
merged 5 commits into from
Jan 31, 2024

Conversation

iamsobanjaved
Copy link
Contributor

@iamsobanjaved iamsobanjaved commented Jan 25, 2024

Upgrade to Django 4.2

Issue: #32833

This is final django42 upgrade PR for production.

  • sandbox created
  • ecommerce checkout working
  • import/export and few celery tasks tested.
  • makemigration does not bring new migration.
  • migrate does not run any hidden migration.
  • sha1 value updated to sha256 in settings.py

Original PR #33211

@awais786
Copy link
Contributor

#33969
Last attempt failed due to one xblock version issue.

iamsobanjaved and others added 2 commits January 26, 2024 07:54
chore: upgrade Django to latest patch version

Commit generated by workflow `openedx/edx-platform/.github/workflows/upgrade-one-python-dependency.yml@refs/heads/master`
…7d53dc

feat: Upgrade Python dependency Django
@iamsobanjaved iamsobanjaved merged commit cd8e2d2 into master Jan 31, 2024
46 checks passed
@iamsobanjaved iamsobanjaved deleted the iamsobanjaved/django-42-lts branch January 31, 2024 10:17
@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX production environment.

1 similar comment
@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX production environment.

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.

5 participants