Skip to content

[staging-25.11] python3Packages.django_4: 4.2.27 -> 4.2.28#486712

Closed
mweinelt wants to merge 1 commit intoNixOS:staging-25.11from
mweinelt:backport-django-4.2.28-to-release-25.11
Closed

[staging-25.11] python3Packages.django_4: 4.2.27 -> 4.2.28#486712
mweinelt wants to merge 1 commit intoNixOS:staging-25.11from
mweinelt:backport-django-4.2.28-to-release-25.11

Conversation

@mweinelt
Copy link
Member

@mweinelt mweinelt commented Feb 3, 2026

https://docs.djangoproject.com/en/4.2/releases/4.2.28/
https://www.djangoproject.com/weblog/2026/feb/03/security-releases/

Fixes: CVE-2025-13473, CVE-2025-14550, CVE-2026-1207, CVE-2026-1285,
CVE-2026-1287, CVE-2026-1312

(cherry picked from commit 154cebd)

cc #486607

Things done

  • Built on platform:
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • Tested, as applicable:
  • Ran nixpkgs-review on this PR. See nixpkgs-review usage.
  • Tested basic functionality of all binary files, usually in ./result/bin/.
  • Nixpkgs Release Notes
    • Package update: when the change is major or breaking.
  • NixOS Release Notes
    • Module addition: when adding a new NixOS module.
    • Module update: when the change is significant.
  • Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

@mweinelt mweinelt added the 1.severity: security Issues which raise a security issue, or PRs that fix one label Feb 3, 2026
@mweinelt mweinelt force-pushed the backport-django-4.2.28-to-release-25.11 branch from 8ce7fe1 to 7da1be7 Compare February 3, 2026 22:15
github-actions[bot]

This comment was marked as resolved.

@nixpkgs-ci nixpkgs-ci bot added 8.has: package (update) This PR updates a package to a newer version 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-darwin: 501+ This PR causes many rebuilds on Darwin and should normally target the staging branches. 11.by: package-maintainer This PR was created by a maintainer of all the package it changes. 10.rebuild-linux: 1001-2500 This PR causes many rebuilds on Linux and should target the staging branches. 10.rebuild-darwin: 501-1000 This PR causes many rebuilds on Darwin and should normally target the staging branches. 9.needs: reviewer This PR currently has no reviewers requested and needs attention. 6.topic: python Python is a high-level, general-purpose programming language. 4.workflow: backport This targets a stable branch labels Feb 3, 2026
@mweinelt mweinelt changed the title [staging-25.11] python3Packages.django_4: 4.2.27 -> 4.2.28] [staging-25.11] python3Packages.django_4: 4.2.27 -> 4.2.28 Feb 3, 2026
@mweinelt
Copy link
Member Author

mweinelt commented Feb 4, 2026

Picked into #483601, because we get it at half the price, because python3Packages.django_4 was mistakenly disabled and needs to be rebuilt anyhow.

@mweinelt mweinelt closed this Feb 4, 2026
@mweinelt mweinelt deleted the backport-django-4.2.28-to-release-25.11 branch February 4, 2026 20:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

1.severity: security Issues which raise a security issue, or PRs that fix one 4.workflow: backport This targets a stable branch 6.topic: python Python is a high-level, general-purpose programming language. 8.has: package (update) This PR updates a package to a newer version 9.needs: reviewer This PR currently has no reviewers requested and needs attention. 10.rebuild-darwin: 501-1000 This PR causes many rebuilds on Darwin and should normally target the staging branches. 10.rebuild-darwin: 501+ This PR causes many rebuilds on Darwin and should normally target the staging branches. 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-linux: 1001-2500 This PR causes many rebuilds on Linux and should target the staging branches. 11.by: package-maintainer This PR was created by a maintainer of all the package it changes.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant