numan: baixar versions anteriors

[0.2.2] - 2026-08-16
Added
- Release assets for aarch64-unknown-linux-gnu and aarch64-pc-windows-msvc (native ARM runners); numan update --self maps those triples
- Homebrew Linux ARM archive support; winget verifies and submits both Windows x64 and ARM64 zips
- numan use activation profiles: cross-minor switches auto-deactivate Numan-active plugins/modules (leave profile is a never-shrinking union per Nu minor in state/activation-profile.json, captured by snapshots and restored on rollback) and restore the target minor's desired set after the marker write. Same-target use is restore-only reconcile. User activate/deactivate keep the current minor's desired set in sync (idempotent even when already active/inactive); remove clears the package id from every minor.
- Intake provenance and evidence tiers:
- Display commit-snapshot provenance (commit hash and captured date) in numan info and package listings (P1).
- Gate and display provisional evidence tier markers (P6).
- Display fork identity and origin metadata for stewardship forks (P4).
- PATH Nu version mismatch warning: detect and warn when the Nu binary on $PATH differs in version or location from the managed active Nu installation.
- Unit test & coverage suites: comprehensive unit test coverage for cmd:: modules and dedicated CI coverage reporting job.
Changed
- numan try: now takes a required <owner/name[@version]> argument and is compatibility-first. It attempts to install and activate the specified package for the current Nu; if incompatible, it explains which managed Nu versions the package supports and recommends the nearest one, without silently switching Nu or installing an alternative package.
- numan completions <shell> installs by default (creates the target directory if needed). Use --print to emit the script on stdout for piping or custom redirects.
- numan registry packages: clearer listing (blank line between entries, styled id/version/type, soft-wrapped dim descriptions).
- numan install: suggests --all flag when a package is incompatible with the current Nu version.
- numan init: added tab-completion configuration hint to first-run output.
- ADR 0001: Accepted Architecture Decision Record for Ecosystem Trust, Upstream Contribution, and Fork Stewardship.
Fixed
- Cached artifact verification: enforce SHA-256 integrity checks on cached archive payloads before extraction.
- Windows User PATH pollution from acceptance tests: PathRestoreGuard sets
a test-only flag that makes persist_path_dir / Unix persist_user_path
skip durable User PATH, ~/.local/bin/nu, and shell-profile writes while the
guard is held (it does not rewrite the Windows User PATH registry on drop, so
concurrent external PATH edits are preserved). numan setup nu / use also
refuse to persist paths under the system temp folder (fail closed if the temp
root cannot be canonicalized), so tempfile fixtures like Temp\.tmp*\off
cannot land on PATH again. If you already have those leftovers, clean User
PATH (PowerShell):
$userPath = [Environment]::GetEnvironmentVariable('Path', 'User')
$cleaned = ($userPath -split ';' | Where-Object {
$_ -and ($_ -notmatch '(?i)\\Temp\\.tmp.*\\(off|existing-nu)$')
}) -join ';'
[Environment]::SetEnvironmentVariable('Path', $cleaned, 'User')
Then open a new terminal and confirm with $env:Path -split ';'.
- numan doctor: report versioned managed Nu installs (tools/nushell/<version>/nu) instead of only the legacy tools/nushell/nu path
- numan setup nu: official Nushell 0.114.x release archives exceed the old
256 MiB extract cap (~279 MiB uncompressed on linux-gnu). Bootstrap now
extracts only the nu binary (skipping bundled plugins) and raises the
uncompressed-size limit to 512 MiB so managed installs succeed again.
Archive-bomb file_count / total_bytes accounting still charges every
regular-file entry scanned, including those skipped by the include filter.
- Homebrew formula install: fix formula installation handling for staged archives.

[0.2.1] - 2026-08-07
Added
- numan update --self: upgrade the numan CLI itself. Standalone installs download the matching GitHub Release asset, verify the Ed25519 signature over SHA256SUMS (SHA256SUMS.sig + baked-in release public key), then check the archive digest and replace the binary. Homebrew / winget / cargo installs print the exact upgrade command instead of self-replacing; --check still queries GitHub Releases to report whether a newer version exists before printing that hint. The Release workflow now hard-fails if NUMAN_RELEASE_SIGNING_KEY is unset so every published release ships SHA256SUMS.sig.
- SECURITY.md: vulnerability reporting, scope, and cross-repo trust summary (linked from the README)
Changed
- numan search / numan info: scripts and completions are labeled install-only (activation deferred) instead of module-style "not ABI-locked" wording; install-only labels still appear when Nu is unknown
- numan try: prefers activatable curated starters (plugin/module), then falls back to Nu-agnostic install-only scripts (SuaveIV/nu_script_wttr, Sanceilaks/nufetch) without calling activate; prints a quoted overlay use path from the installed lockfile entry

[0.2.0] - 2026-08-05
Added
- Homebrew tap packaging restored: brew tap tonythethompson/numan && brew install numan, with Publish to Homebrew tap updating homebrew-numan from release SHA256SUMS (requires HOMEBREW_TAP_TOKEN)
- Side-by-side Nu version management via numan use <version>|latest|list:
- Switches the active managed Nushell install without re-downloading (errors with numan setup nu <version> hint when the requested version isn't installed yet)
- Writes <root>/nu_state/active-version.json so numan use list and downstream activation can resolve the selected Nu
- Acquires the root mutation lock and creates a PreMutation snapshot before any state change, matching install/update/activate/deactivate
- numan setup nu versioned layout: binaries now install under <root>/tools/nushell/<version>/nu instead of the previous single-binary <root>/tools/nushell/nu. Re-installing one version no longer clobbers another. numan doctor reports markers whose on-tree binary is missing.
- Journaled legacy managed-Nu migration from the single-binary layout into the versioned tree, with numan doctor auto-tier reconciliation
- Strict version-path validation (<root>/tools/nushell/<version>/...): rejects components containing /, \\, .., or anything semver won't parse, so numan setup nu ../../path cannot escape $NUMAN_ROOT.
- Shared confirmation utility (src/util/confirm.rs): consistent prompt/auto-confirm behavior across all commands
- Snapshots capture and restore nu_state/paths.json when present
Removed
- Prebuilt macOS Intel (x86_64-apple-darwin) release archives and Homebrew bottles. Apple Silicon and cargo install numan-cli remain supported.
Changed (breaking)
- numan setup nu CLI redesign: action flags (--remove, --use-path, --use-existing) are replaced by subcommands:
- numan setup nu — install latest (unchanged)
- numan setup nu <VERSION> — install pinned version (was --version <x.y.z>)
- numan setup nu remove — uninstall managed Nu (was --remove)
- numan setup nu path — use PATH Nu (was --use-path)
- numan setup nu use <path> — register a specific binary (was --use-existing <path>)
- Hidden backward-compat flags (--remove, --use-path, --use-existing) still work but emit deprecation warnings. They will be removed in v0.3.0.
- Non-TTY auto-confirm: all confirmation prompts now auto-confirm on non-TTY (CI, scripts) instead of requiring --yes. A (non-interactive: auto-confirming) notice is printed to stderr. --yes remains available to skip prompts on TTY.

[0.1.5] - 2026-07-29
Added
- numan setup nu installs an official managed Nushell release, optionally pinned with --version; --use-existing repairs an off-PATH installation without downloading another copy
- numan setup loader installs the bundled nushell-loader integration
- Compatibility-aware discovery: search hides incompatible packages by default (--all reveals them), info explains version compatibility, and install errors report the actual Nu/platform mismatch
- numan try installs and activates a curated starter compatible with the current Nu and platform, with managed-Nu pin offers when no starter matches
- Doctor findings distinguish PATH and managed Nu versions and report the built-in official trust-root identity
- Install support for .tar.xz / .txz package archives (alongside .zip, .tar.gz/.tgz, and .tar)
- numan completions nushell (alias nu) via clap_complete_nushell, with a vendor-autoload install hint
- Active-plugin mutation gate (Issue #22 PR1): refuse remove/update while a plugin activation record exists; doctor info activation.plugin_mutation_gated (docs/active-plugin-gate.md)
- Journaled plugin deactivate (Issue #22 PR2): numan deactivate unregisters via injectable plugin rm seam, clears PluginActivation without deleting payload; pending journal state/pending-plugin-deactivate.json
- Active-plugin update orchestration (Issue #22 PR3): default off; only exact NUMAN_ENABLE_ACTIVE_PLUGIN_MUTATION=1 enables deactivate→upgrade→reactivate via the activate/deactivate-owned cmd::plugin_lifecycle boundary
- Cross-platform real-Nu acceptance coverage for active-plugin update, plus a Windows official-registry Stage 1 lifecycle harness
Fixed
- Autoload journal recovery is command-independent and reconciles pending state before later mutations
- Managed Nu bootstrap verifies release-asset size and SHA256 metadata, validates the installed binary, cleans up failed downloads, and discovers supported off-PATH installations more reliably
- numan try gives actionable managed-Nu pin or package-search guidance when no curated starter matches, without silently switching Nu
- PowerShell completions no longer emit top-of-script using namespace directives, so numan completions powershell can be appended to an existing $PROFILE without a ParserError
- README PowerShell install used Out-File (overwrites $PROFILE); docs now use Add-Content or a dedicated completions file
Changed
- numan remove --force no longer bypasses active plugin activation (still bypasses active module activation only)
- Active-plugin gate hint directs users to numan deactivate <pkg> then numan remove <pkg>
- Active-plugin update is fail-closed and opt-in (default off; only exact NUMAN_ENABLE_ACTIVE_PLUGIN_MUTATION=1 enables it; unset or alternative values refuse); remove remains gated until deactivate
- Official registry Stage 1 acceptance: after list, run deactivate → remove → gc
- numan completions prints a copy-ready install command on stderr after the script (stdout stays pipe-safe)
- WinGet uses the all-lowercase tonythethompson.numan identifier and publishes update PRs automatically after each GitHub release; unsupported Homebrew packaging was removed