Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: pnpm/action-setup
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v6.0.5
Choose a base ref
...
head repository: pnpm/action-setup
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v6.0.6
Choose a head ref
  • 2 commits
  • 8 files changed
  • 1 contributor

Commits on May 4, 2026

  1. fix: update pnpm to 11.0.4

    zkochan committed May 4, 2026
    Configuration menu
    Copy the full SHA
    e578e19 View commit details
    Browse the repository at this point in the history

Commits on May 7, 2026

  1. fix: bin_dest output points to self-updated pnpm, not bootstrap (#249)

    * fix: bin_dest output points to self-updated pnpm, not bootstrap (#247)
    
    `pnpm self-update <version>` writes the target binary to
    `${PNPM_HOME}/bin/`, leaving the bootstrap symlink at `${PNPM_HOME}/pnpm`
    untouched. The `bin_dest` output was set to `${PNPM_HOME}`, so consumers
    invoking `${{ steps.pnpm.outputs.bin_dest }}/pnpm` got the bootstrap
    version (currently 11.0.4) instead of the version they requested.
    
    PATH lookup hid the bug: `${PNPM_HOME}/bin` was prepended ahead of
    `${PNPM_HOME}`, so `pnpm` resolved from PATH was the right one. Existing
    version-respect tests only checked `pnpm --version`, not `bin_dest`.
    
    Resolve `binDest` inside `runSelfInstaller` (target lives in
    `${PNPM_HOME}/bin` after self-update, otherwise stays at `${PNPM_HOME}`)
    and plumb it through to `setOutputs`. Add a regression test that invokes
    `${bin_dest}/pnpm --version` directly across Linux/macOS/Windows.
    
    * test(ci): pass bin_dest via env to survive Windows backslashes
    
    Direct GitHub-expression interpolation of `${{ steps.pnpm.outputs.bin_dest }}`
    into the bash script let bash eat the backslashes in the Windows path
    (`C:Usersrunneradminsetup-pnpmnode_modules.binbin/pnpm`), failing with
    "No such file or directory". Forward the value via env so the path
    reaches bash unmangled.
    
    * build: rebuild dist with clean lockfile-matched deps
    zkochan authored May 7, 2026
    Configuration menu
    Copy the full SHA
    91ab88e View commit details
    Browse the repository at this point in the history
Loading