A .ps1 runs inside the caller's PowerShell process, so the values the
Windows release script exported from .env outlived the script. A
later run in the same session kept the old GITEA_TOKEN even after .env
was edited, because existing environment variables take precedence.
- Read .env into a script-local table and resolve settings through
Get-Setting, with environment variables still taking precedence
- Stop changing the caller's current location; build and archive
with paths anchored at the repository root
- Skip .env lines without "=" instead of failing under StrictMode