Skip to content

Consolidate csp_nonce usages to a single property on the toolbar. #2099

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

Merged
merged 2 commits into from
Mar 14, 2025

Conversation

tim-schilling
Copy link
Member

@tim-schilling tim-schilling commented Mar 8, 2025

Checklist:

  • I have added the relevant tests for this change.
  • I have added an item to the Pending section of docs/changes.rst.

@tim-schilling tim-schilling marked this pull request as ready for review March 14, 2025 22:09
@tim-schilling tim-schilling merged commit 43ec028 into django-csp-4.0 Mar 14, 2025
53 checks passed
@tim-schilling tim-schilling deleted the django-csp-4.0-public branch March 14, 2025 22:09
@@ -25,7 +25,7 @@ deps =
pygments
selenium>=4.8.0
sqlparse
django-csp<4
django-csp
Copy link
Contributor

Choose a reason for hiding this comment

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

Since the django-csp v4 releases are beta, a pre-release, will this pick up v3.8, the last published release? I'm not up on if the intention here is to test against v4 or v3.x but I believe django-csp has solved this issue for both versions anyway by adding the CheckableLazyObject in the v4 betas.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, we test against pre-releases in ci. I think that's why we caught this early.

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.

2 participants