update nixpkgs lock after mailman change

[leona-ya]

PL-133981

@flyingcircusio/release-managers

Release process

• Created changelog entry using ./changelog.sh

PR release workflow (internal)

• PR has internal ticket
• internal issue ID (PL-…) part of branch name
• internal issue ID mentioned in PR description text
• ticket is on Platform agile board
• ticket state set to Pull request ready
• if ticket is more urgent than within the next few days, directly contact a member of the Platform team

• set urgency and risk labels
• ensure the merge bot has determined a merge date
• ensure all checks are green
• get a review from a colleague

Design notes

• Provide a feature toggle if the change might need to be adjusted/reverted quickly depending on context. Consider whether the default should be on or off. Example: rate limiting.
• All customer-facing features and (NixOS) options need to be discoverable from documentation. Add or update relevant documentation such that hosted and guided customers can understand it as well.

Security implications

• Security requirements defined? (WHERE)
• Security requirements tested? (EVIDENCE)
  • dry-build on our mailman host, ensuring that the system configuration builds again (see mailman: do not require nginx uwsgiPass option nixpkgs#1116)

[github-actions]

This PR is ready to merge. Merge scheduled for 2025-11-05