Django 3.2.21 security patch

[magajh]

Apply the 3.2.21 security patch to Palm branches.

Open edX services to upgrade

Beta Give feedback

1. edx-platform
2. enterprise-catalog
3. enterprise-access
4. ecommerce
5. edx-analytics-data-api
6. edx-analytics-dashboard
7. credentials
8. xqueue
9. ecommerce-worker
10. tubular
11. edx-notes-api
12. license-manager
13. course-discovery
14. blockstore
15. taxonomy-connector
16. registrar
17. openedxstats

[magajh]

Hey @mariajgrimaldi, I'm tagging you here in case we want to keep track of this issue for the next Palm release #302 :)

[mariajgrimaldi]

Once you have a list of PR(s), please add them here so we can help review them. Thanks!

[mariajgrimaldi]

What's the procedure when there's a new security patch while the previous ones haven't been merged? A progressive update by patch order?

[magajh]

@mariagrimaldi A progressive update doesn't seem necessary, as patch 3.2.22 is compatible with version 3.2.20. I think we can close this issue, close any remaining open PRs, and then create new PRs to apply the 3.2.22 patch to the respective repositories

[magajh]

Update: We're shifting our focus to the latest Django security patch 3.2.23. As a result, this issue and any open PRs related to the Django 3.2.21 patch will be closed.

Please see the new issue for the 3.2.23 patch here: Issue #306.