AU: 1 updated - vlc-nightly

[skip ci] https://gist.github.com/675e3f672bda54270f8d7f5415f9374d/f5a3dd62d2f4e65029e36392af1053b911ecc369
mkevenaar · Apr 11, 2022 · 5ce540b · 5ce540b
1 parent abe41eb
commit 5ce540b
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 5 deletions.
diff --git a/automatic/vlc-nightly/legal/VERIFICATION.txt b/automatic/vlc-nightly/legal/VERIFICATION.txt
@@ -7,19 +7,19 @@ Package can be verified like this:
 
 1. Go to
 
-   x64: https://artifacts.videolan.org/vlc/nightly-win64/20220410-0421/vlc-4.0.0-dev-win64-2d52141e.exe
+   x64: https://artifacts.videolan.org/vlc-3.0/nightly-win64/20220411-0220/vlc-3.0.17.3-win64-4e17d578.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: 4D710C1B1E6E1DBFE0B3A1555C81B776E16430E84D1865B895CF4E7ABF2C7D8A
+   checksum64: B0D57D5704B774B866E8BDD892C229D9BCE9919E16906D03909A2CDE480C212D
 
 Using AU:
 
-   Get-RemoteChecksum https://artifacts.videolan.org/vlc/nightly-win64/20220410-0421/vlc-4.0.0-dev-win64-2d52141e.exe
+   Get-RemoteChecksum https://artifacts.videolan.org/vlc-3.0/nightly-win64/20220411-0220/vlc-3.0.17.3-win64-4e17d578.exe
 
 File 'LICENSE.txt' obtained from:
    https://git.videolan.org/?p=vlc.git;a=blob_plain;f=COPYING;hb=HEAD
diff --git a/automatic/vlc-nightly/vlc-nightly.json b/automatic/vlc-nightly/vlc-nightly.json
@@ -1,4 +1,4 @@
 {
-    "3.0":  "3.0.17.320220410",
+    "3.0":  "3.0.17.320220411",
     "4.0":  "4.0.0.20220410"
 }
diff --git a/automatic/vlc-nightly/vlc-nightly.nuspec b/automatic/vlc-nightly/vlc-nightly.nuspec
@@ -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>4.0.0.20220410</version>
+    <version>3.0.17.320220411</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>
     <!-- ============================== -->