v0.2.0

First 0.2.0 minor release — the largest feature surface shipped so far: named, persisted language/tool version pins usable from any directory, not just inside a stack-managed project.

Added

• stack profile — interactive wizard: pick languages (same checkbox flow as stack new), then choose to activate it in this shell, save it under a name, or both.
• stack profile <name> — activate a saved profile in the current shell.
• stack profile <name> --exec "<command>" — resolve a profile's pins (installing anything missing), run a one-off command with them on PATH, then exit. Nothing persists.
• stack profile list / describe <name> / edit <name> / rm <name> — manage saved profiles.
• stack deactivate — clear an explicitly-activated profile. A project's own cd-based activation is unaffected.
• stack which / stack which <name> — show exactly what stack would resolve a language/tool to right now, and why (current project, active profile, or the reserved default-named profile as a final fallback).
• stack exec --with php@8.3.1,node@20 -- <command> — ephemeral ad hoc version pins with no named profile at all.
• stack setup --default-profile <name> — ambiently auto-activate a profile in every new terminal (--default-profile none to clear).
• stack prune now also scans ~/.stack/profiles/*.toml, so a profile's pinned language versions are never mistaken for orphaned installs.

Changed

• stack's PowerShell shell hook now also applies an active/default profile's PATH additions on every prompt, alongside the current project's — profile and project pins combine, with the project winning on conflict.
• Fresh PHP installs no longer force opcache.enable_cli on.

Install

irm https://github.com/sanayasfp/stack/releases/latest/download/stackenv-installer.ps1 | iex

or

cargo install stackenv