ci: bump rhysd/action-setup-vim from 1.4.1 to 1.6.1

[dependabot]

Bumps rhysd/action-setup-vim from 1.4.1 to 1.6.1.

Release notes

Sourced from rhysd/action-setup-vim's releases.

v1.6.1

This is a small patch update for security fixes.

• Update major versions of @actions/* packages including some security fixes in HTTP client.
• Update glob and js-yaml indirect dependencies for security fixes.
• Update the major version of proxy-from-env that disables the support for the legacy npm_config_-prefixed environment variables.

v1.6.0

• Add new vim-dir output which stores the $VIM directory absolute path of the installation. See :help $VIM for more details about the directory. This output is useful to locate where the Vim/Neovim is installed by the following steps. Here is an example of setting the installation-specific vimrc configuration:

  - uses: rhysd/action-setup-vim@v1
    id: vim
  - name: Setup vimrc specific to the Vim installation
    run: |
      cp vimrc_for_ci.vim '${{ vim.vim-dir }}/vimrc'

• Fix the Vim installation directory structure on Windows. It did not conform the standard directory layout which Vim assumes (though it worked fine for compatibility reasons). Previously the runtime directory was wrongly squashed. The paths before/after this release when installing stable version are:
  • Previous wrong path: ~/vim-stable/vim.exe
  • New correct path: ~/vim-stable/vim91/vim.exe
• Clean up temporary directories created by this action after installation completes. Temporary directories containing downloaded assets were not removed previously but they could cause troubles when installing multiple Vim/Neovim instances.
• Report logs via core.info() instead of directly calling console.log().

v1.5.1

• Fix installing stable Vim on macos-15-intel runner. It was broken again after v1.4.5 release due to the change in the upstream runner. (#52)
• Update @actions/io to v2.0.0 for better Node.js v24 support.

v1.5.0

• Support arm64 native binaries on windows-11-arm runner.
  • When an arm64 binary is missing in the release due to some reasons (e.g. build error), it falls back to x86_64 binary so that your workflow can continue. In this case the x86_64 binary is executed via x86 emulation.
  • Neovim only supports arm64 binaries on nightly builds for now.
• Migrate the action runtime from node20 to node24. This change only affects users running this action on self-hosted runners.
• Fix the validation for installed executables was not sufficient on Windows.

v1.4.5

• Better workaround for #52 to properly install stable Vim on macos-15-intel runner. We use python@3.13 package which is already installed on the system instead of installing python package to remove conflicted symbolic links. It's faster and has less side effects.

v1.4.4

• Fix stable Vim installation fails on macos-15-intel runner due to the version conflict in python Homebrew package. (#52)
• Fix HTTPS proxy is not used when accessing GitHub API via Octokit client even if https_proxy environment variable is set.
• Fix using a deprecated API in node-fetch package.

v1.4.3

• Use HTTPS proxy looking at environment variables such as https_proxy, no_proxy, all_proxy when fetching assets. (#50, thanks @​xieyonn)
• Implementation migrated from CommonJS to ES Modules. This should not affect the behavior of this action.
• Reduce amount of log output when installing stable Vim on Linux.
• Update dependencies including @actions/github.

v1.4.2

• Fix the version of stable Neovim or Vim may be outdated on macOS by updating formulae before running brew install. By this fix, the new version of Neovim which was released 2 days ago is now correctly installed. (#49)
• Add a warning message with useful information when executing ./configure fails to build older versions of Vim.

... (truncated)

Changelog

Sourced from rhysd/action-setup-vim's changelog.

v1.6.1 - 2026-03-18

This is a small patch update for security fixes.

• Update major versions of @actions/* packages including some security fixes in HTTP client.
• Update js-yaml indirect dependency for security fix.
• Update glob indirect dependency for security fix.
• Update the major version of proxy-from-env that disables the support for the legacy npm_config_-prefixed environment variables.

[Changes][v1.6.1]

v1.6.0 - 2025-11-09

• Add new vim-dir output which stores the $VIM directory absolute path of the installation. See :help $VIM for more details about the directory. This output is useful to locate where the Vim/Neovim is installed by the following steps. Here is an example of setting the installation-specific vimrc configuration:

  - uses: rhysd/action-setup-vim@v1
    id: vim
  - name: Setup vimrc specific to the Vim installation
    run: |
      cp vimrc_for_ci.vim '${{ vim.vim-dir }}/vimrc'

• Fix the Vim installation directory structure on Windows. It did not conform the standard directory layout which Vim assumes (though it worked fine for compatibility reasons). Previously the runtime directory was wrongly squashed. The paths before/after this release when installing stable version are:
  • Previous wrong path: ~/vim-stable/vim.exe
  • New correct path: ~/vim-stable/vim91/vim.exe
• Clean up temporary directories created by this action after installation completes. Temporary directories containing downloaded assets were not removed previously but they could cause troubles when installing multiple Vim/Neovim instances.
• Report logs via core.info() instead of directly calling console.log().

[Changes][v1.6.0]

v1.5.1 - 2025-11-02

• Fix installing stable Vim on macos-15-intel runner. It was broken again after v1.4.5 release due to the change in the upstream runner. (#52)
• Update @actions/io to v2.0.0 for better Node.js v24 support.

[Changes][v1.5.1]

v1.5.0 - 2025-10-26

• Support arm64 native binaries on windows-11-arm runner.
  • When an arm64 binary is missing in the release due to some reasons (e.g. build error), it falls back to x86_64 binary so that your workflow can continue. In this case the x86_64 binary is executed via x86 emulation.
  • Neovim only supports arm64 binaries on nightly builds for now.
• Migrate the action runtime from node20 to node24. This change only affects users running this action on self-hosted runners.
• Fix the validation for installed executables was not sufficient on Windows.

... (truncated)

Commits

• febef33 Release v1.6.1 at 96eb633a04e4bf2eea5ecc4cc6727cef90c1f21d
• 19e3dd3 Release v1.6.0 at cc7d353df19540d8a9c9d330b788f97d62b5f91e
• 46cf85a Release v1.5.1 at a8f077550a6f1334de0ae31f5604eca144090bd5
• 387ddb8 Release v1.5.0 at 278c9f5621e428281aee81b019925dabfe526164
• 1bba848 Release v1.4.5 at 8df38d89d40040d4fd9158cedb9398e81699266b
• b6be9a9 Release v1.4.4 at dce2c28dd1061a5b9a292a501964fedbd9bdb76a
• 89f3345 Release v1.4.3 at d67fb332289f4e289e0e13cac889eae44e2ac3c5
• 8e931b9 Release v1.4.2 at 5d1c22fc4d347a7efe0937568804aaebd2087e7f
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)