Cherry-Pick Check Report: Attention Required

ci/check-cherry-picks.md

30ca1c1bd9e5c5f99b5ff3ff258eaae614c656952d941be000000003000003cd

This report is automatically generated by the `check-cherry-picks` CI workflow.

Some of the commits in this PR have not been cherry-picked exactly and require the author's and reviewer's attention.

Please make sure to follow the [backporting guidelines](https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#how-to-backport-pull-requests) and cherry-pick with the `-x` flag. This requires changes to go to the unstable branches (`master` / `staging`) first, before backporting them.

Occasionally, it is not possible to cherry-pick exactly the same patch. This most frequently happens when resolving merge conflicts while cherry-picking or when updating minor versions of packages which have already advanced to the next major on unstable. If you need to merge this PR despite the warnings, please [dismiss](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review) this review.

Chunks

9d04b39f (1st chunk of `ci/check-cherry-picks.md`)

Title: Cherry-Pick Check Report: Attention Required

Summary

This is an automated report from the `check-cherry-picks` CI workflow, indicating that some commits in the pull request have not been cherry-picked exactly. It instructs the author and reviewer to ensure they follow backporting guidelines, using the `-x` flag during cherry-picking, and prioritizing changes to unstable branches first. If exact cherry-picking is impossible, the review can be dismissed after careful consideration.