Skip to content

941 upgrade django 4.2.24#946

Merged
jsjiang merged 3 commits intodevelopfrom
941_upgrade_django_4.2.24
Sep 10, 2025
Merged

941 upgrade django 4.2.24#946
jsjiang merged 3 commits intodevelopfrom
941_upgrade_django_4.2.24

Conversation

@jsjiang
Copy link
Copy Markdown
Contributor

@jsjiang jsjiang commented Sep 10, 2025

@sfisher Hi Scott,
This is to upgrade Django 4.2.24 to address security issue #941. The branch was created from the main branch which contains two merge related commits that the develop branch does not have. I was trying to merge the main branch to the develop branch to have it in sync with main. However the new branch protection rule "no merge without pull request" blocked it. I hope the 2 merge related commits will not cause issue when we merge the develop branch to the main for production deployment.

UI and functional tests all look good on ezid-stg with a testing tag test-django-4.2.24.

Please take a look and let me know if you have questions.

Jing

jsjiang and others added 3 commits July 28, 2025 14:45
Merge Develop to the main branch
Pull request to merge develop to main
@jsjiang jsjiang requested review from Copilot and sfisher September 10, 2025 00:20
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR upgrades Django from version 4.2.22 to 4.2.24 to address security issue #941. This is a security patch update that maintains compatibility within the Django 4.2.x series.

  • Django version upgrade from 4.2.22 to 4.2.24
  • Security vulnerability remediation

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@jsjiang
Copy link
Copy Markdown
Contributor Author

jsjiang commented Sep 10, 2025

Also updated documentation on how to upgrade Django https://github.com/CDLUC3/ezid-docs-internal/pull/30

Copy link
Copy Markdown
Contributor

@sfisher sfisher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for updating this. It looks good to me, Jing.

I think the merge of main to develop or develop to main will be fine. :-)

@jsjiang jsjiang merged commit 5fc43fa into develop Sep 10, 2025
2 checks passed
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.

3 participants