chore: upgrade Django 4.2

[raymond1242]

Description

Django 4.2 Upgrade

Testing considerations

• Include instructions for any required manual tests, and any manual testing that has
  already been performed.
• Include unit and a11y tests as appropriate
• Consider performance issues.
• Check that Database migrations are backwards-compatible

Post-review

Squash commits into discrete sets of changes

[openedx-webhooks]

Thanks for the pull request, @raymond1242! 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.

[mphilbrick211]

Hi @raymond1242! Just flagging that there's a failing check.

[raymond1242]

Hi Michelle. I realized the mistake, and will fix it ASAP

…

On Fri, Sep 15, 2023 at 8:53 AM Michelle Philbrick ***@***.***> wrote: Hi @raymond1242 <https://github.com/raymond1242>! Just flagging that there's a failing check. — Reply to this email directly, view it on GitHub <#518 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH5BEJPWZSBEWO6EFOQKLCTX2RMWZANCNFSM6AAAAAA4PPEZ2E> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[raymond1242]

Hi @mphilbrick211! I fixed the error, could you please approve the workflows

[raymond1242]

Hi @mphilbrick211, I have already completed all the steps of the issue and all tests were green, due to main branch updating conflict I had to rebase the branch to solve conflicts and it sends another approval check, that's the reason tests are yellow now. I'm waiting for your approval and review 🙌🏻.
Additionally, I created this thread where I comment the approach used and future improvements.

[mphilbrick211]

Thanks @raymond1242! I will look into getting tests run for you.

[e0d]

@raymond1242 looks like there are some failures. Can you have a look? It's possible some code related to your changes changed out from under you.

[mphilbrick211]

@raymond1242 looks like there are some failures. Can you have a look? It's possible some code related to your changes changed out from under you.

Hi @raymond1242! Just following up on this :)

[mphilbrick211]

Hi @raymond1242 - just checking in to see if you plan on pursuing this pull request?

CC: @openedx/build-test-release-wg-security-patchers - just in case someone can push this through if needed.

[raymond1242]

Hi @mphilbrick211, I'm going to remove this PR

[openedx-webhooks]

@raymond1242 Even though your pull request wasn’t merged, please take a moment to answer a two question survey so we can improve your experience in the future.