Skip to content

Commit

Permalink
AU: 2 updated - vlc-nightly vscode-ansible
Browse files Browse the repository at this point in the history
  • Loading branch information
mkevenaar committed Nov 17, 2022
1 parent 8ca65f9 commit 38875b0
Show file tree
Hide file tree
Showing 5 changed files with 7 additions and 7 deletions.
6 changes: 3 additions & 3 deletions automatic/vlc-nightly/legal/VERIFICATION.txt
Original file line number Diff line number Diff line change
Expand Up @@ -7,19 +7,19 @@ Package can be verified like this:

1. Go to

x64: https://artifacts.videolan.org/vlc-3.0/nightly-win64/20221117-0220/vlc-3.0.18-win64-638a07db.exe
x64: https://artifacts.videolan.org/vlc/nightly-win64/20221117-0427/vlc-4.0.0-dev-win64-b0db51a2.exe

to download the installer.

2. You can use one of the following methods to obtain the SHA256 checksum:
- Use powershell function 'Get-FileHash'
- Use Chocolatey utility 'checksum.exe'

checksum64: 993BD4E6F03AE9CE15C22746875EAD3823F81857D67065028B99BE1F4BE4EFD8
checksum64: AA9229FC87167E112D1C00E2761ED3C38637E4A5996480369F440471059D6A90

Using AU:

Get-RemoteChecksum https://artifacts.videolan.org/vlc-3.0/nightly-win64/20221117-0220/vlc-3.0.18-win64-638a07db.exe
Get-RemoteChecksum https://artifacts.videolan.org/vlc/nightly-win64/20221117-0427/vlc-4.0.0-dev-win64-b0db51a2.exe

File 'LICENSE.txt' obtained from:
https://git.videolan.org/?p=vlc.git;a=blob_plain;f=COPYING;hb=HEAD
2 changes: 1 addition & 1 deletion automatic/vlc-nightly/vlc-nightly.json
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
{
"3.0": "3.0.18.20221117",
"4.0": "4.0.0.20221116"
"4.0": "4.0.0.20221117"
}
2 changes: 1 addition & 1 deletion automatic/vlc-nightly/vlc-nightly.nuspec
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ This is a nuspec. It mostly adheres to https://docs.nuget.org/create/Nuspec-Refe
<!-- version should MATCH as closely as possible with the underlying software -->
<!-- Is the version a prerelease of a version? https://docs.nuget.org/create/versioning#creating-prerelease-packages -->
<!-- Note that unstable versions like 0.0.1 can be considered a released version, but it's possible that one can release a 0.0.1-beta before you release a 0.0.1 version. If the version number is final, that is considered a released version and not a prerelease. -->
<version>3.0.18.20221117</version>
<version>4.0.0.20221117</version>
<!-- owners is a poor name for maintainers of the package. It sticks around by this name for compatibility reasons. It basically means you. -->
<owners>Maurice Kevenaar</owners>
<!-- ============================== -->
Expand Down
2 changes: 1 addition & 1 deletion automatic/vscode-ansible/tools/chocolateyInstall.ps1
Original file line number Diff line number Diff line change
Expand Up @@ -3,4 +3,4 @@
# clean up old extension
Uninstall-VsCodeExtension -extensionId 'vscoss.vscode-ansible'

Install-VsCodeExtension -extensionId 'redhat.ansible@1.0.96'
Install-VsCodeExtension -extensionId 'redhat.ansible@1.0.97'
2 changes: 1 addition & 1 deletion automatic/vscode-ansible/vscode-ansible.nuspec
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ This is a nuspec. It mostly adheres to https://docs.nuget.org/create/Nuspec-Refe
<!-- version should MATCH as closely as possible with the underlying software -->
<!-- Is the version a prerelease of a version? https://docs.nuget.org/create/versioning#creating-prerelease-packages -->
<!-- Note that unstable versions like 0.0.1 can be considered a released version, but it's possible that one can release a 0.0.1-beta before you release a 0.0.1 version. If the version number is final, that is considered a released version and not a prerelease. -->
<version>1.0.96</version>
<version>1.0.97</version>
<!-- owners is a poor name for maintainers of the package. It sticks around by this name for compatibility reasons. It basically means you. -->
<owners>Maurice Kevenaar</owners>
<!-- ============================== -->
Expand Down

0 comments on commit 38875b0

Please sign in to comment.