feat: add tool-versions-file option to run-script

### what

an a `tool-versions-file` parameter to the `run-script` workflow to allow
selecting a different file from `.tool-versions`

### why

Allow use CI-specific tooling without having `mise` pick them up by default in
the repo

### testing

will test in workflows

### docs

updated docs

Author: albertodonato

.github/workflows/run-script.yml

@@ -18,6 +18,10 @@ on:
         type: boolean
         description: "Expose the job's read-only GitHub token to the script as GH_TOKEN"
         default: false
+      tool-versions-file:
+        type: string
+        description: "Name of the mise tool versions file. A bare filename, looked up from the working directory up to the repository root"
+        default: ".tool-versions"
     secrets:
       STEP_SECURITY_API_KEY:
         required: false
@@ -29,6 +33,7 @@ jobs:
       contents: read
     env:
       HARDEN_RUNNER: ${{ secrets.STEP_SECURITY_API_KEY != '' }} # zizmor: ignore[secrets-outside-env]
+      MISE_DEFAULT_TOOL_VERSIONS_FILENAME: ${{ inputs.tool-versions-file }}
     steps:
       - name: Harden Runner
         if: env.HARDEN_RUNNER == 'true'
@@ -48,6 +53,8 @@ jobs:
         with:
           minimum_release_age: 7d
           cache: true
+          # The default cache key only hashes .tool-versions, so add the custom file.
+          cache_key: "{{cache_key_prefix}}-{{platform}}-{{file_hash}}-${{ hashFiles(format('**/{0}', inputs.tool-versions-file)) }}"
 
       # Always read the cache, it's safe to do so even on untrusted PRs.
       - name: Restore pre-commit cache

README.md

@@ -34,6 +34,10 @@ commits never get one, so a SHA is what names the commit you meant.
 
 Run a set of commands on the repository, with the required tools installed via `mise`.
 
+Tools are read from `.tool-versions` by default. Set `tool-versions-file` to use a
+different file: it must be a bare filename (not a path), which mise looks up from the
+working directory up to the repository root.
+
 
 ```
   Lint: