Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Build ReleaseOS when a PR is from a fork rather than Release.
This fixes OSS PR builds which, until now, have been failing because they cannot access secrets.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
workflow_dispatch
|
|
|
|
|
|
|
|
|
|
|
|
Start trimming trailing whitespace, but limit the blast radius to a
handful of file types.
|
|
Fix channel detection for mac builds
|
|
|
|
|
|
a release
|
|
Since downstream jobs reference the output of the new `setvar` job, instead of
directly referencing global `env.RELEASE_RUN`, no need to set `RELEASE_RUN` in
the global environment.
|
|
not the string "false", which is true.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Update from main
|
|
|
|
github.repository
|
|
github.repository
|
|
from branch name in builds
|
|
|
|
Move towards packaging artifacts with xz, which offers higher compression ratios and faster decode time.
|
|
Drop python version from matrix configuration as it's always 3.11.
|
|
# Conflicts:
# .github/workflows/build.yaml
|
|
|
|
|
|
|
|
From https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#using-secrets-in-a-workflow :
"Secrets cannot be directly referenced in if: conditionals. Instead, consider
setting secrets as job-level environment variables, then referencing the
environment variables to conditionally run steps in the job."
|
|
The previous construct produced:
Unrecognized named-value: 'secrets'. Located at position 1 within expression:
secrets.AZURE_KEY_VAULT_URI && ...
|