[albertodonato]

what

add a mise-env parameter to the run-script workflow to set MISE_ENV, so
that mise.<env>.toml config files are loaded on top of the default config.

Also requires lockfile.

why

Allow using CI-specific tooling without having mise pick it up by default in
the repo

testing

will test in workflows

docs

updated docs

🤖 Generated with Claude Code

[cubic-dev-ai]

All reported issues were addressed across 2 files

Architecture diagram

sequenceDiagram
    participant Admin as GitHub Actions Admin
    participant WF as run-script Workflow
    participant Action as step-security/action
    participant Setup as Setup Job (setup-mise)
    participant Cache as Pre-commit Cache
    participant Mise as mise Tool Manager
    participant Script as User Script

    Note over Admin,Script: Private CI Workflow for Mise-Provisioned Scripts

    Admin->>WF: Trigger workflow with inputs
    Note right of Admin: inputs.<br/>tool-versions-file (default .tool-versions)

    WF->>WF: Set MISE_DEFAULT_TOOL_VERSIONS_FILENAME env<br/>from inputs.tool-versions-file

    WF->>Action: Harden Runner
    Action-->>WF: Secured environment

    WF->>Setup: Setup Job
    Setup->>Setup: Install mise
    Setup->>Mise: Read tools from<br/>MISE_DEFAULT_TOOL_VERSIONS_FILENAME
    Mise->>Mise: Search working dir up to repo root<br/>for configured filename
    alt Custom tool-versions-file provided
        Mise-->>Setup: Load tools from custom file
    else Default .tool-versions
        Mise-->>Setup: Load tools from .tool-versions
    end
    Setup-->>WF: Tools ready

    WF->>Cache: Restore pre-commit cache
    Cache->>Cache: Compute cache key with<br/>custom tool-versions filename hash
    alt Cache hit
        Cache-->>WF: Restore cache
    else Cache miss
        Cache-->>WF: No cache
    end

    WF->>Script: Execute user script
    Script->>Mise: Use provisioned tools (available on PATH)
    Mise-->>Script: Tool binaries
    Script-->>WF: Script result (success/failure)

Loading

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 1 file (changes from recent commits).

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Re-trigger cubic</sub>