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 Mar 6, 2024
1 parent 9541fd8 commit aa96783
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 @@
"0222ca6144ae10cc0b87794ff42eca8a"|22.1.0.0
"19226ceb54a86aef472a74d336e4ce0a"|22.2.0.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 = 'C3C63AE7E4B54736200671649AE191ADAB42193EF56330C2C5838551147371C8'
$checksum = '06A74548B3279B2A329139AB3E3D6D3EDD52CEB291918DC0DB57DDFBE1693503'
$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.1.0.0</version>
<version>22.2.0.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 aa96783

Please sign in to comment.