AU: 1 updated - vlc-nightly

[skip ci] https://gist.github.com/675e3f672bda54270f8d7f5415f9374d/3c5c5b959e9c3b209759cb2680c98728f64ba763
mkevenaar · Sep 26, 2022 · e1c729a · e1c729a
1 parent f9be0b4
commit e1c729a
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/20220926-0220/vlc-3.0.18-win64-915f83e3.exe
+   x64: https://artifacts.videolan.org/vlc/nightly-win64/20220926-0430/vlc-4.0.0-dev-win64-426ff68e.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: A66D500A6E130435FC388F200C1891FAC58CA4A4FD77987457F79BF7C4D20489
+   checksum64: C0A8EE8DF713737DB0C7B257AD368CC62F95CC73219747DA115671B68B46C866
 
 Using AU:
 
-   Get-RemoteChecksum https://artifacts.videolan.org/vlc-3.0/nightly-win64/20220926-0220/vlc-3.0.18-win64-915f83e3.exe
+   Get-RemoteChecksum https://artifacts.videolan.org/vlc/nightly-win64/20220926-0430/vlc-4.0.0-dev-win64-426ff68e.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.20220926",
-    "4.0":  "4.0.0.20220925"
+    "4.0":  "4.0.0.20220926"
 }
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.20220926</version>
+    <version>4.0.0.20220926</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>
     <!-- ============================== -->