v0.1.4

Upgrade notes

• Azure: every job gets a new name on its next deploy. The name is pdt-<app>-<7 hex characters>, with a maximum of 32 characters. The deploy plan shows delete Container Apps Job <old> (its name is now <new>). destroy, pdt secrets, pdt runs, and pdt logs still find a job that has the old name. (#80)
• Azure: set again each secret that you set with pdt secrets <app> set in 0.1.3 or earlier. Those versions stored the value under the app name, not under the variable name. (#87)

New

• A folder of .ps1 files with no run.py is an app. pdt installs PowerShell 7 and the modules that the scripts need, and runs the scripts through a built-in wrapper. run.ps1, run_scripts, continue_on_error, and pdt new APP --from-scripts control it. A cloud image builds from a separate Dockerfile that installs the modules at build time. (#120)
• pdt -h shows the commands in groups. (#82)
• A command that takes an app name uses the current app folder when you leave the name off. (#117)

Fixes

• AWS: pdt starts the pinned AWS CLI from the uv cache with --offline after the first install. A failed request to GitHub no longer stops the command. (#103)
• deploy --all, and a run.py started from the project root, read the .env of each app. (#124)
• Off Windows, every windows provider command stops with one error. (#119)