fix(ci): write bun installer to RUNNER_TEMP on Windows ARM

[l2ysho]

Closes #1221.

The Install bun (Windows ARM) step downloaded install.ps1 into the repo checkout (cwd), leaving an untracked file. The next step's pnpm version … --allow-same-version runs a git status --porcelain clean-tree check, which then aborts with ERR_PNPM_UNCLEAN_WORKING_TREE — flakily, since a re-run starts clean.

Fix: download and run the installer from $env:RUNNER_TEMP instead of the repo root, in both release.yaml and pre_release.yaml. The working tree stays clean.

[l2ysho]

I did not like this idea of claude actually, after quick research probably --no-git-checks in pre-release step is far better solution, but feel free to discuss.

 run: pnpm version ${{ needs.release_metadata.outputs.version_number }} --no-git-tag-version --allow-same-version --no-git-checks  

[vladfrangu]

Will this even be needed post my PR that fixes arm64 windows builds?

[DaveHanns]

I did not like this idea of claude actually, after quick research probably --no-git-checks in pre-release step is far better solution, but feel free to discuss.

 run: pnpm version ${{ needs.release_metadata.outputs.version_number }} --no-git-tag-version --allow-same-version --no-git-checks  

Not fully sure, but --no-git-checks might backfire in the future as it disables the check whether a working tree is clean completely 🤔
Installing into temp directory seems like a cleaner and reusable (if ever needed again) solution to me.

[l2ysho]

Will this even be needed post my PR that fixes arm64 windows builds?

Actually you fix it with that PR. Probably best thing to do, but lets keep in mind this new pnpm 11 behaviour.

[l2ysho]

I did not like this idea of claude actually, after quick research probably --no-git-checks in pre-release step is far better solution, but feel free to discuss.

 run: pnpm version ${{ needs.release_metadata.outputs.version_number }} --no-git-tag-version --allow-same-version --no-git-checks  

Not fully sure, but --no-git-checks might backfire in the future as it disables the check whether a working tree is clean completely 🤔 Installing into temp directory seems like a cleaner and reusable (if ever needed again) solution to me.

actually --no-git-checks is how it worked in pnpm@10 out of the box, we had a dirty worktree, it just did not care. This is second/third breaking change I experienced in v11, probably I should take a look at the changelog.

[DaveHanns]

I did not like this idea of claude actually, after quick research probably --no-git-checks in pre-release step is far better solution, but feel free to discuss.

 run: pnpm version ${{ needs.release_metadata.outputs.version_number }} --no-git-tag-version --allow-same-version --no-git-checks  

Not fully sure, but --no-git-checks might backfire in the future as it disables the check whether a working tree is clean completely 🤔 Installing into temp directory seems like a cleaner and reusable (if ever needed again) solution to me.

actually --no-git-checks is how it worked in pnpm@10 out of the box, we had a dirty worktree, it just did not care. This is second/third breaking change I experienced in v11, probably I should take a look at the changelog.

Alright, good to know :D

[l2ysho]

Closing this due to #1169

[l2ysho]

I will hot fix this as I am blocked in release process, revert and fix will be done in #1169 cc @patrikbraborec @DaveHanns