[staging 24.11] vim: 9.1.0787 -> 9.1.1006

[philiptaron]

Resolves GHSA-5rgf-26wj-48v8.

vim/vim@v9.1.0787...v9.1.1006

I've scanned through this set of commit messages and don't see anything that is breaking-change worthy, and the changes to https://github.com/vim/vim/blame/master/runtime/doc/version9.txt back that up. This is normal for Vim.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

[philiptaron]

Staging PR: #372980

[mweinelt]

The commits are not picked with the -x flag, meaning they don't refer to the commit they were picked from.

[philiptaron]

The commits are not picked with the -x flag, meaning they don't refer to the commit they were picked from.

Ah, so in order to have this be a PR "in order", the staging PR must be merged first?

[philiptaron]

Converting to draft until staging PR #372980 is merged.

[vcunat]

You could do the same with commits that aren't merged yet. At least if you believe that they won't change hash (amend, rebase, etc.)