AU: 1 updated - vlc-nightly

[skip ci] https://gist.github.com/675e3f672bda54270f8d7f5415f9374d/69b6c2e51c26314fa93434e67b07808ecd580f27
mkevenaar · Nov 18, 2022 · 1a96060 · 1a96060
1 parent cc728f4
commit 1a96060
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/20221117-0427/vlc-4.0.0-dev-win64-b0db51a2.exe
+   x64: https://artifacts.videolan.org/vlc-3.0/nightly-win64/20221118-0219/vlc-3.0.18-win64-bbf81b68.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: AA9229FC87167E112D1C00E2761ED3C38637E4A5996480369F440471059D6A90
+   checksum64: A32B6CC6F60F152AE4AF0EF8CDD73493213879C866CA28EC7A2C8EE40484BF73
 
 Using AU:
 
-   Get-RemoteChecksum https://artifacts.videolan.org/vlc/nightly-win64/20221117-0427/vlc-4.0.0-dev-win64-b0db51a2.exe
+   Get-RemoteChecksum https://artifacts.videolan.org/vlc-3.0/nightly-win64/20221118-0219/vlc-3.0.18-win64-bbf81b68.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.20221117",
+    "3.0":  "3.0.18.20221118",
     "4.0":  "4.0.0.20221117"
 }
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.20221117</version>
+    <version>3.0.18.20221118</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>
     <!-- ============================== -->