diff options
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | 2020-10-07 08:17:49 (GMT) |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2020-10-07 16:54:53 (GMT) |
| commit | 17c13069b47e64fb3fdd4de57f87b80943be1e4d (patch) | |
| tree | 7b563dfb8dae82d8273e74fd25a9b6828165cc10 /.github | |
| parent | d98273ba77e1ab9ec755576bc86c716a97bf59d7 (diff) | |
| download | git-17c13069b47e64fb3fdd4de57f87b80943be1e4d.zip git-17c13069b47e64fb3fdd4de57f87b80943be1e4d.tar.gz git-17c13069b47e64fb3fdd4de57f87b80943be1e4d.tar.bz2 | |
GitHub workflow: automatically follow minor updates of setup-msbuild
It is the custom to follow minor updates of GitHub Actions
automatically, by using the suffix `@v1`. Actions' maintainers will then
update that `v1` ref to point to the newest.
However, for `microsoft/setup-msbuild`, 889cacb6897 (ci: configure
GitHub Actions for CI/PR, 2020-04-11) uses a very specific `@v1.0.0`
suffix.
In this instance, that is a problem: should `setup-msbuild` release a
new version that intends to fix a critical bug, we won't know it, and we
won't use it.
Such a scenario is not theoretical. It is happening right now:
https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands
Let's simplify our setup, allowing us to benefit from automatically
using the newest v1.x.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to '.github')
| -rw-r--r-- | .github/workflows/main.yml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml index fcfd138..14ff94d 100644 --- a/.github/workflows/main.yml +++ b/.github/workflows/main.yml @@ -154,7 +154,7 @@ jobs: Expand-Archive compat.zip -DestinationPath . -Force Remove-Item compat.zip - name: add msbuild to PATH - uses: microsoft/setup-msbuild@v1.0.0 + uses: microsoft/setup-msbuild@v1 - name: copy dlls to root shell: powershell run: | |