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

Update to Django 3.2 (for TUP CMS) #626

Merged
merged 17 commits into from
May 3, 2023
Merged

Conversation

wesleyboar
Copy link
Member

@wesleyboar wesleyboar commented Apr 24, 2023

Overview

Update Django to v3.2 and bump deprecated dependencies, for tup-cms.

Related

Changes

  • update dependencies
  • rename …-cms to …_cms (e.g. example-cms to example_cms)
  • rename …-org to …_org (e.g. texascale-org to texascale_org)

Testing

  1. Build Core-CMS image.
  2. Either spin up TUP-CMS locally.
    Or deploy TUP CMS on dev server.
  3. Verify CMS allows add/publish/delete pages.
  4. Verify assets are loaded and pages are unchanged from before deploy.
  5. Follow test steps on feat(tup-cms): update django to v3.2 tup-ui#225.

UI

See TACC/tup-ui#225.

Notes

#625 requires to many updates (to Core-CMS-Resources), and we want to update TUP ASAP, so this branch and PR is made.

Known Issues

See TACC/tup-ui#225.

@wesleyboar wesleyboar changed the title Update to Django 3.2 (for TUP-CMS) Update to Django 3.2 (for TUP CMS) Apr 24, 2023
@wesleyboar wesleyboar mentioned this pull request Apr 24, 2023
@wesleyboar wesleyboar added the priority ▲▲ Very high priority label Apr 24, 2023
@wesleyboar wesleyboar marked this pull request as ready for review May 2, 2023 23:13
@wesleyboar wesleyboar marked this pull request as draft May 2, 2023 23:14
@wesleyboar wesleyboar marked this pull request as ready for review May 3, 2023 15:51
@wesleyboar wesleyboar merged commit 9ff0f1e into dev/tup-cms May 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority ▲▲ Very high priority
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant