Django 4.2 upgrade

[alexyanque]

⛔️ DEPRECATION WARNING

This repository is deprecated and in maintainence-only operation while we work on a replacement, please see this announcement for more information.

Although we have stopped integrating new contributions, we always appreciate security disclosures and patches sent to [email protected]

Issue: edx/#206

Anyone internally merging to this repository is expected to release and monitor their changes; if you are not able to do this DO NOT MERGE, please coordinate with someone who can to ensure that the changes are released.

Merge checklist:

• Any new requirements are in the right place (do not manually modify the requirements/*.txt files)
  • base.in if needed in production
  • test.in for test requirements
  • make upgrade && make requirements have been run to regenerate requirements
• Version bumped

Post merge:

• Tag pushed and a new version released
  • Note: Assets will be added automatically. You just need to provide a tag (should match your version number) and title and description.
• After versioned build finishes in GitHub CI, verify version has been pushed to PyPI
  • Each step in the release build has a condition flag that checks if the rest of the steps are done and if so will deploy to PyPi.
    (so basically once your build finishes, after maybe a minute you should see the new version in PyPi automatically (on refresh))
• PR created in ecommerce to upgrade dependencies (including ecommerce-worker)
  • This must be done after the version is visible in PyPi as make upgrade in ecommerce will look for the latest version in PyPi.
  • Note: the ecommerce-worker constraint in ecommerce must also be bumped to the latest version in PyPi.
• Deploy ecommerce
• Deploy ecomworker on GoCD.
  • While some functions in ecommerce-worker are run via ecommerce, others are handled by a standalone AMI and must be
    released via GoCD.

[openedx-webhooks]

Thanks for the pull request, @alexyanque! Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

• supporting documentation
• Open edX discussion forum threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

[e0d]

@alexyanque
I notice there are some commit-lint failures. Please note that we use conventional commits across Open edX projects. You can read about the details here. Can you please amend your commit messages to follow our standard?

[mphilbrick211]

Hi @openedx/revenue-squad! This is ready for review.