Repository navigation
Releases
Releases · saeid-adz/azup
azup 2.7.1
Immutable
release. Only release title and notes can be modified.
- Same as the never-published 2.7.0 (its tag could not be released), now released as 2.7.1.
- Now on PyPI as
azup-cli:pipx install azup-cli(the command is stillazup). - Windows executable:
azup.exeis attached to every release (single file, no Python needed), with a SHA-256 checksum. Scheduled updates and the terminal nudge work from the exe too. azup self-updaterecognises how azup was installed (exe / winget, Homebrew, pip/pipx) and points to the matching upgrade command instead of overwriting a managed install.- Releases are now built and published by a tag-triggered workflow (PyPI Trusted Publishing, no stored tokens).
azup 2.6.1 – kubelogin on Windows
Fixed
- Windows:
azup install kubeloginfailed with No package found matching input criteria. The correct winget id isMicrosoft.Azure.Kubelogin.
Added
- CI check that every winget id used by azup exists in the winget package repository.
Workaround before updating: winget install --id Microsoft.Azure.Kubelogin -e
azup 2.6.0 – parallel installs & updates
New
- Parallel installs and updates with a live status board. Work runs in lanes (Homebrew, PowerShell Az, PowerShell Graph/Entra, az, azd, winget, tarball) side by side.
- Homebrew formulas are batched into one
brewcall (Homebrew downloads in parallel itself; azup retries one by one if the batch fails). - Steps wait for what they depend on (PowerShell → modules, az → extensions, azd → azd extensions) and fail clearly if it failed.
- Anything that may prompt (macOS casks, trusting a tap) still runs on its own with a real terminal.
-j/--jobs N(default 4,-j 1= one at a time, envAZUP_JOBS) on install, update and select.
Measured with simulated tools: 12 installs 35 s → 9 s. Verified for real on macOS (concurrent PowerShell Gallery installs in a clean profile). The winget, tarball and Linux lanes use the same engine but haven't been run on those systems yet.
azup 2.5.0 – what's new, nudges & auto-update
New
- What's new before updating –
azup changes [tools],azup update --changes, andcat the Proceed? prompt show release notes for just the versions between yours and the latest. - Terminal nudge –
azup nudge enable: one short line when you open a terminal if tools are outdated (at most daily, instant start, opt-in, removable). - Scheduled updates –
azup schedule enable|disable|statusvia launchd / systemd (or cron) / Task Scheduler. Unattended runs never prompt, skip anything needing a password, log to~/.azup/logs.
Fixed
azup install az/update azpicked the Az PowerShell module instead of Azure CLI.az= Azure CLI,Az= PowerShell module; aliasesazps,graph,entra.
Scheduling on Linux and Windows is new and was verified only by generating the configuration – please report problems.
azup 2.3.0 – whoami, ctx and Foundry
New
azup whoami– who you're signed in as in az, azd, Az PowerShell and Graph, with a warning when they disagree.azup ctx– switch subscription in az, azd and Az PowerShell at once. Type-to-filter picker;azup ctx <name|id>jumps straight there.- AI / Foundry –
azup install --profile ai: Foundry Local (Windows/macOS), azd extensions (microsoft.foundry,azure.ai.agents) with an azd minimum-version check, and themlextension for az. azup login --tenant <id>; new menu entries.
azup 2.2.2 – Windows launcher fix
Fixed
- Windows:
azupfailed with Unknown option: -3. The installer-generated launcher quoted-3, so thepylauncher passed it to python.exe. Re-run the installer, or patch the existing launcher (see below).
(Get-Content $HOME\.azup\bin\azup.cmd) -replace '"-3"','-3' | Set-Content $HOME\.azup\bin\azup.cmd -Encoding ASCIIazup 2.2.1 – fresh Windows 11 installs
Fixed
- Windows installer failed on a fresh Windows 11 (Python 3.8+ not found and winget is unavailable). It now registers winget if needed and otherwise installs Python directly from python.org (per user, no admin needed).
- azup registers winget (App Installer) itself when it is missing.
azup 2.2.0 – PowerShell on Linux, properly
New
- Linux: PowerShell is installed from Microsoft's official release tarball into
~/.local– no snap, no sudo, SHA-256 verified, andazup updatekeeps it current. - A tool that is on PATH but doesn't start (e.g. a broken snap
pwsh) is now treated as not installed, so azup can install a working one.
Needs ICU on Linux: sudo apt install -y libicu-dev (Debian/Ubuntu).
azup 2.1.2 – Linux fixes
Fixed
- Homebrew: packages left installed but not linked (seen with Functions Core Tools after the tap-trust retry) are now linked automatically.
- PowerShell: azup checks that
pwshstarts before installing modules, and explains the problem once with diagnostics instead of failing every module.
azup 2.1.1 – Azzy gets a new look
Azzy is now an Azure-style A with eyes (light left half, dark right half) in the terminal, the README demo and the banner. It's an original drawing, not the official Azure logo.