AU: 3 updated - nsis nsis.install nsis.portable

[skip ci] https://gist.github.com/mkevenaar/675e3f672bda54270f8d7f5415f9374d/c39f95fb52e023a50ebf2c80e47651da9cf554e9

automatic/nsis.install/legal/VERIFICATION.txt

@@ -6,12 +6,12 @@ The installer have been downloaded from their official download link listed on <
 and can be verified like this:
 
 1. Download the following installers:
-  32-Bit: <https://sourceforge.net/projects/nsis/files/NSIS%203/3.09/nsis-3.09-setup.exe/download>
+  32-Bit: <https://sourceforge.net/projects/nsis/files/NSIS%203/3.10/nsis-3.10-setup.exe/download>
 2. You can use one of the following methods to obtain the checksum
   - Use powershell function 'Get-Filehash'
   - Use chocolatey utility 'checksum.exe'
 
   checksum type: sha256
-  checksum32: B06AAFCC8F06C504FA15F2994A85086E7CDAE4B786CE52CE9D812DC1EFEAC2F9
+  checksum32: 4313D352E0DAFD1F22B6517126A655CAE3B444FA758D2845EDDFBE72F24F7BDD
 
 File 'LICENSE.txt' is obtained from <https://nsis.sourceforge.io/License>

automatic/nsis.install/nsis.install.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.09</version>
+    <version>3.10</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>
     <!-- ============================== -->

automatic/nsis.install/tools/chocolateyInstall.ps1

@@ -3,7 +3,7 @@ $toolsDir              = "$(Split-Path -parent $MyInvocation.MyCommand.Definitio
 
 $packageArgs = @{
   packageName    = $env:ChocolateyPackageName
-  file           = "$toolsDir\nsis-3.09-setup.exe"
+  file           = "$toolsDir\nsis-3.10-setup.exe"
   fileType       = 'exe'
   softwareName   = 'Nullsoft Install System*'
   silentArgs     = '/S'

automatic/nsis.portable/legal/VERIFICATION.txt

@@ -6,12 +6,12 @@ The installer have been downloaded from their official download link listed on <
 and can be verified like this:
 
 1. Download the following installers:
-  32-Bit: <https://sourceforge.net/projects/nsis/files/NSIS%203/3.09/nsis-3.09.zip/download>
+  32-Bit: <https://sourceforge.net/projects/nsis/files/NSIS%203/3.10/nsis-3.10.zip/download>
 2. You can use one of the following methods to obtain the checksum
   - Use powershell function 'Get-Filehash'
   - Use chocolatey utility 'checksum.exe'
 
   checksum type: sha256
-  checksum32: F5DC52EEF1F3884230520199BAC6F36B82D643D86B003CE51BD24B05C6BA7C91
+  checksum32: FCDCE3229717A2A148E7CDA0AB5BDB667F39D8FB33EDE1DA8DABC336BD5AD110
 
 File 'LICENSE.txt' is obtained from <https://nsis.sourceforge.io/License>

automatic/nsis.portable/nsis.portable.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.09</version>
+    <version>3.10</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>
     <!-- ============================== -->

automatic/nsis.portable/tools/chocolateyInstall.ps1

@@ -4,7 +4,7 @@ $toolsDir     = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
 $packageArgs = @{
   packageName    = $env:ChocolateyPackageName
   Destination    = $toolsDir
-  FileFullPath   = "$toolsDir\nsis-3.09.zip"
+  FileFullPath   = "$toolsDir\nsis-3.10.zip"
 }
 
 Get-ChocolateyUnzip  @packageArgs

automatic/nsis/nsis.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.09</version>
+    <version>3.10</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>
     <!-- ============================== -->
@@ -68,7 +68,7 @@ let them know [here](https://github.com/mkevenaar/chocolatey-packages/issues) th
 
     <!-- Specifying dependencies and version ranges? https://docs.nuget.org/create/versioning#specifying-version-ranges-in-.nuspec-files -->
     <dependencies>
-      <dependency id="nsis.install" version="[3.09]" />
+      <dependency id="nsis.install" version="[3.10]" />
     </dependencies>
 
     <!--<provides>NOT YET IMPLEMENTED</provides>-->