| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
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 && ...
|
|
Specifically, when secrets aren't available (e.g. for external PRs), skip the
affected steps.
|
|
Mark issues as stale but do not close them.
|
|
|
|
instead of the branch that got pulled.
(cherry picked from commit b42e01d7acf5d4c55612c3a7df0e1ff6ee5ed951)
|
|
instead of on the current tag 7.1.2-release.
(cherry picked from commit 27b298d8bc720ff315c8e74cc5bff9ff9ead0552)
|
|
This should (!) allow us to generate full release notes relative to the
previous viewer release, instead of letting action-gh-release guess
incorrectly.
Also try again to add to the release page a back-link to the specific build.
(cherry picked from commit 88ebb92f05dade00cc8fc519cc062a458ecd48f2)
|
|
(cherry picked from commit 4edd78f2e54b3cd2e0b0a4b9300dfc669231dd98)
|
|
Using github.ref as action-gh-release's target_commitish produces:
⚠️ GitHub release failed with status: 422
[{"resource":"Release","code":"invalid","field":"target_commitish"}]
(cherry picked from commit c6a6db8488a8b3e7ea6534fbf5e2fe2b17864421)
|
|
Also try to cross-reference release page and build page.
(cherry picked from commit a908b4cfa98716d4a838fc1e5a6789faa15d16cf)
|
|
Put whatever release notes we retrieve into the generated release page.
(cherry picked from commit ff543b744ee0b0fd4dd90b46419ae50a570572ab)
|
|
Now that which_branch.py has moved to viewer-build-util, so has the PyGithub
dependency.
(cherry picked from commit dd0ec112fe5ded8ed5f69b72b3df26343ca12d35)
|
|
which_branch.py has moved to viewer-build-util as a reusable action.
(cherry picked from commit 09f66828ba573515c3766cce32f4746b8189efcf)
|
|
(cherry picked from commit 2c5066f1fcc0c9f145698ef3aaec72d27bce7181)
(cherry picked from commit ff1741cecae0fac6d94507fa4a6e4662219af707)
|
|
in viewer's autobuild-package.xml.
Ensure that AUTOBUILD_VCS_BRANCH is set before the build.
(cherry picked from commit b782ab73e640e434e4ed67fa8dfc951f09757585)
(cherry picked from commit 6e8d4f48466a5bbad2fcc27bc2877a30e575d4ce)
|
|
The release job has been dependent on sign-and-package-windows and
sign-and-package-mac, each of which depends on build. But that indirect
dependency doesn't convey access to ${{ needs.build.outputs.xxx }}. Add the
build job to direct dependencies so release can access its outputs.
(cherry picked from commit 819604d2cee6d4527cc436bebfacddf8642635ff)
|
|
(cherry picked from commit 6654ad14eed674e894d2903e0f2ea37c4e806c0f)
|
|
(cherry picked from commit 59eeaed1187e7592fd83380045916f2d8b9d58e7)
|
|
For a tag build that generates a release page, try to deduce the git branch to
which the tag we're building corresponds and add that to release notes.
(cherry picked from commit 9e99bb04a32f2ecc0f0b99686ce5a7adb356596d)
|
|
(cherry picked from commit f71662225eadf1589f5331e763e02e0bb1b72137)
|
|
|
|
instead of the branch that got pulled.
|
|
instead of on the current tag 7.1.2-release.
|
|
This should (!) allow us to generate full release notes relative to the
previous viewer release, instead of letting action-gh-release guess
incorrectly.
Also try again to add to the release page a back-link to the specific build.
|
|
|
|
Using github.ref as action-gh-release's target_commitish produces:
⚠️ GitHub release failed with status: 422
[{"resource":"Release","code":"invalid","field":"target_commitish"}]
|
|
Also try to cross-reference release page and build page.
|
|
|
|
making ordering explicit, and disabling blank issue submission to force
triage label to be set.
|
|
|
|
|
|
|
|
Issue template for the "blank issue" option
|
