AU: 1 updated - vlc-nightly

[skip ci] https://gist.github.com/675e3f672bda54270f8d7f5415f9374d/be3a60fe08d8c6d036a7c826dafeb5694abdd59c
mkevenaar · Oct 10, 2022 · de28c84 · de28c84
1 parent efc50c5
commit de28c84
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/20221010-0219/vlc-3.0.18-rc2-win64-4b5506e3.exe
+   x64: https://artifacts.videolan.org/vlc/nightly-win64/20221010-0425/vlc-4.0.0-dev-win64-5be2ef66.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: 203A30704D33128BED6D91CE2B77725DF8EB833EC988129FD2940CF0A3273304
+   checksum64: 1FF3BBFA3C2037E99F844FFBC5E5FFFF4A8BC897036B7278224F0BDC6E3C5DCF
 
 Using AU:
 
-   Get-RemoteChecksum https://artifacts.videolan.org/vlc-3.0/nightly-win64/20221010-0219/vlc-3.0.18-rc2-win64-4b5506e3.exe
+   Get-RemoteChecksum https://artifacts.videolan.org/vlc/nightly-win64/20221010-0425/vlc-4.0.0-dev-win64-5be2ef66.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.20221010",
-    "4.0":  "4.0.0.20221009"
+    "4.0":  "4.0.0.20221010"
 }
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.20221010</version>
+    <version>4.0.0.20221010</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>
     <!-- ============================== -->