Skip to content

v0.2.1

Choose a tag to compare

View all tags
@sanayasfp sanayasfp released this 04 Aug 09:02
· 6 commits to main since this release
v0.2.1
de0c9f7

Follow-up to v0.2.0, fixing three real bugs in stack setup --default-profile and adding structured profile modification.

Fixed

  • stack deactivate was a silent no-op whenever a default profile was configured — the per-prompt shell hook re-seeded the profile activation on the very next prompt. --default-profile no longer touches shell-session state at all (see Changed below), which removes the bug entirely.
  • The [stack] prompt indicator lit up for any profile-provided PATH, not just being inside a project. It now only reflects project activation, as before profiles existed.
  • Explicit stack profile <name> activation silently skipped a profile's [tool.*] entries on PATH, even though stack exec and the default-profile mechanism both included them.
  • Editing, adding to, or removing from a profile that's the current default no longer leaves the persistent PATH stale — it's refreshed automatically.

Changed

  • stack setup --default-profile <name> now resolves the profile's pins and writes them directly into the persistent Windows user PATH (via the registry), instead of seeding a per-prompt shell variable. A brand-new process — interactive or not, stack-aware or not — now finds its languages/tools with zero dependency on any shell hook. Note: already-running terminals/IDEs need a restart to pick up the change, same as installing anything else that touches PATH.

Added

  • stack profile add <name> <language|tool> <entry> [version] [flags] and stack profile remove <name> <language|tool> <entry> — structured modification of a saved profile, mirroring stack add/stack remove on stack.toml.

Install

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

or

cargo install stackenv
Assets 8
Loading