Skip to content

Commit

Permalink
AU: 1 updated - viber
Browse files Browse the repository at this point in the history
  • Loading branch information
mkevenaar committed Feb 9, 2024
1 parent 5b8f041 commit 8372db3
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion automatic/viber/info
@@ -1 +1 @@
"cfca04160998b41bbb02bdc85568bfa3"|22.0.0.0
"5a2170d24cbdece834cfe36810cd2255"|22.0.1.0
2 changes: 1 addition & 1 deletion automatic/viber/tools/chocolateyInstall.ps1
Expand Up @@ -2,7 +2,7 @@

$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url = 'https://download.cdn.viber.com/desktop/windows/ViberSetup.exe'
$checksum = '1E4FF69CAFDCD30E2AC3DFCE5A5243EFB7228D1EF295CD536FFE0160DF5C0D5C'
$checksum = 'A0C6BB8BF1524DF61574F910C456953D05B74FE790B4D3310BD04F7CF18EF230'
$checksumType = 'sha256'
$packageArgs = @{
packageName = $env:ChocolateyPackageName
Expand Down
2 changes: 1 addition & 1 deletion automatic/viber/viber.nuspec
Expand Up @@ -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>22.0.0.0</version>
<version>22.0.1.0</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>
<!-- ============================== -->
Expand Down

0 comments on commit 8372db3

Please sign in to comment.