AU: 1 updated - vlc-nightly

[skip ci] https://gist.github.com/675e3f672bda54270f8d7f5415f9374d/3e277b631b854cdecf4f6770f3bea842443520c6
mkevenaar · Oct 2, 2022 · 0063925 · 0063925
1 parent 902cbfd
commit 0063925
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-3.0/nightly-win64/20221002-0225/vlc-3.0.18-rc2-win64-fef232f9.exe
+   x64: https://artifacts.videolan.org/vlc/nightly-win64/20221002-0425/vlc-4.0.0-dev-win64-0b13cf8b.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: 74C0D8716C572E6D5A98BBD620AFF05A5F6970C7A3A4795ACA80A0A1393A134F
+   checksum64: 0B652124586E02B242E3C7F3CEE08B3B6D7DD83B3434B1CBA48D09A4BB591E6F
 
 Using AU:
 
-   Get-RemoteChecksum https://artifacts.videolan.org/vlc-3.0/nightly-win64/20221002-0225/vlc-3.0.18-rc2-win64-fef232f9.exe
+   Get-RemoteChecksum https://artifacts.videolan.org/vlc/nightly-win64/20221002-0425/vlc-4.0.0-dev-win64-0b13cf8b.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.18.20221002",
-    "4.0":  "4.0.0.20221001"
+    "4.0":  "4.0.0.20221002"
 }
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>3.0.18.20221002</version>
+    <version>4.0.0.20221002</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>
     <!-- ============================== -->