Downloads:

1,425,683

Downloads of v 85.0.4171.0-snapshots:

123

Last Update:

13 Jun 2020

Package Maintainer(s):

Software Author(s):

  • The Chromium Authors

Tags:

chromium admin google cross-platform foss chrome browser

Chromium Snapshots

This is a prerelease version of Chromium Snapshots.

  • 1
  • 2
  • 3

85.0.4171.0-snapshots | Updated: 13 Jun 2020

Downloads:

1,425,683

Downloads of v 85.0.4171.0-snapshots:

123

Maintainer(s):

Software Author(s):

  • The Chromium Authors

Tags:

chromium admin google cross-platform foss chrome browser

  • 1
  • 2
  • 3
 Chromium Snapshots 85.0.4171.0-snapshots

This is a prerelease version of Chromium Snapshots.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

To install Chromium Snapshots, run the following command from the command line or from PowerShell:

>

To upgrade Chromium Snapshots, run the following command from the command line or from PowerShell:

>

To uninstall Chromium Snapshots, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://community.chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade chromium -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade chromium -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Ensure chromium installed
  win_chocolatey:
    name: chromium
    state: present
    version: 85.0.4171.0-snapshots
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'chromium' do
  action    :install
  version  '85.0.4171.0-snapshots'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: chromium,
    Version: 85.0.4171.0-snapshots,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller chromium
{
   Name     = 'chromium'
   Ensure   = 'Present'
   Version  = '85.0.4171.0-snapshots'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'chromium':
  provider => 'chocolatey',
  ensure   => '85.0.4171.0-snapshots',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install chromium version="85.0.4171.0-snapshots" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 13 Jun 2020.

Description

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. This site contains design documents, architecture overviews, testing information, and more to help you learn to build and work with the Chromium source code.

Notes

  • This package installs by default to the %programfiles(x86)% instead of %localappdata%\Chromium.
  • If you have installed this package in the past to the %localappdata%\Chromium location it will continue to be installed in this location.
legal\LICENSE.txt 
// Copyright 2015 The Chromium Authors. All rights reserved.
//
// Redistribution and use in source and binary forms, with or without
// modification, are permitted provided that the following conditions are
// met:
//
//    * Redistributions of source code must retain the above copyright
// notice, this list of conditions and the following disclaimer.
//    * Redistributions in binary form must reproduce the above
// copyright notice, this list of conditions and the following disclaimer
// in the documentation and/or other materials provided with the
// distribution.
//    * Neither the name of Google Inc. nor the names of its
// contributors may be used to endorse or promote products derived from
// this software without specific prior written permission.
//
// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
legal\VERIFICATION.txt 
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The embedded software have been downloaded from the listed download
location on <https://github.com/henrypp/chromium/releases/> (the listed mirrors may differ from the used mirror below)
and can be verified by doing the following:

1. Download the following:
  32-Bit software: <https://storage.googleapis.com/chromium-browser-snapshots/Win/777947/mini_installer.exe>
  64-Bit software: <https://storage.googleapis.com/chromium-browser-snapshots/Win_x64/777943/mini_installer.exe>
2. Get the checksum using one of the following methods:
  - Using powershell function 'Get-FileHash'
  - Use chocolatey utility 'checksum.exe'
3. The checksums should match the following:

  checksum type: sha256
  checksum32: 2A6F7B89491220AD7E9EA758A0961CC70E482EDBEE9B4CFF65E49A9BCD8348E6
  checksum64: 3DA9B396E62EFCC63D378F868F32CE8033A83850DE1EC6A21D5840893AF42A6A

The file 'LICENSE.txt' has been obtained from <https://chromium.googlesource.com/chromium/src.git/+/master/LICENSE>
tools\chocolateyInstall.ps1 
$ErrorActionPreference = 'Stop'
$scriptDir=$toolsDir = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
. (Join-Path $scriptDir 'helper.ps1')

$version = "85.0.4171.0-snapshots"
$hive = "hkcu"
$chromium_string = "\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Chromium"
$Chromium = $hive + ":" + $chromium_string

if (Test-Path $Chromium) {
  $silentArgs = '--do-not-launch-chrome'
} else {
  $silentArgs = '--system-level --do-not-launch-chrome'
}

$packageArgs = @{
  packageName   = 'chromium'
  file          = "$toolsdir\chromium_x32.exe"
  file64        = "$toolsdir\chromium_x64.exe"
  fileType      = 'exe'
  silentArgs    = $silentArgs
  validExitCodes= @(0)
  softwareName  = 'Chromium'
}
if ( Get-CompareVersion -version $version -notation "-snapshots" -package "chromium" ) {
Install-ChocolateyInstallPackage @packageArgs 
} else {
Write-Host "Chromium $version is already installed."
}
Remove-Item $toolsDir\*.exe -ea 0 -force
tools\chocolateyUninstall.ps1 
$registry = Get-UninstallRegistryKey -SoftwareName "chromium*"
$file = $registry.UninstallString
$Arg_chk = ($file -match "--system-level")
$chromiumArgs = @{$true = "--uninstall --system-level"; $false = "--uninstall"}[ $Arg_chk ]
$silentArgs = @{$true = '--uninstall --system-level --force-uninstall'; $false = '--uninstall --force-uninstall'}[ $Arg_chk ]
$myfile = $file -replace ( $chromiumArgs )
# All arguments for the Uninstallation of this package
$packageArgs = @{
  PackageName    = 'Chromium'
  FileType       = 'exe'
  SilentArgs     = $silentArgs
  validExitCodes = @(0, 19, 21)
  File           = $myfile
}
# Now to Uninstall the Package
Uninstall-ChocolateyPackage @packageArgs
# This at the moment does not remove the libs\Chromium folder
tools\chromium_x32.exe 
md5: 8B97CA7094ADE1DF89D52D328DBF1E3D | sha1: 524CF23600E7CD884B726AB70C81A2836FCE3CAB | sha256: 2A6F7B89491220AD7E9EA758A0961CC70E482EDBEE9B4CFF65E49A9BCD8348E6 | sha512: EB5212908CA2344D0281C64E592D5DEC42735B26BC191CF4604B830D3F2791377CBEC59F8957F5D23F4A06C301F0807AB0DFA93F39BF85795D1124054402B89E
tools\chromium_x64.exe 
md5: C7A254D5923E55A7E4B57EA476FB718C | sha1: 31AC79AF85B169EAC6A9B1D25F2289D2BA7B9F65 | sha256: 3DA9B396E62EFCC63D378F868F32CE8033A83850DE1EC6A21D5840893AF42A6A | sha512: 7259F8CAD40C2039FB5CF6281BB935CFCE4025AA7A11C1E40E4DE71D0F4A5E68BC2D9D6F041DF0BAC8C81CF3C5EEBDE93BD281BF4A6C6DE35476EE78744CCB9F
tools\helper.ps1 

function Get-CompareVersion {
  param(
    [string]$version,
    [string]$notation,
    [string]$package
  )
	$vorgehen = $true;
    $packver = @{$true = $version; $false = ($version -replace($notation,""))}[ ( $version -notmatch $notation ) ]
    [array]$key = Get-UninstallRegistryKey -SoftwareName "$package*"
    if ($packver -eq ( $key.Version )) {
	  $vorgehen = $false
    }
    return $vorgehen
  }

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Chromium Snapshots 97.0.4677.0-snapshots 16 Wednesday, October 20, 2021 Approved
Chromium Snapshots 97.0.4675.0-snapshots 29 Tuesday, October 19, 2021 Approved
Chromium Snapshots 97.0.4674.0-snapshots 22 Monday, October 18, 2021 Approved
Chromium Snapshots 97.0.4673.0-snapshots 23 Sunday, October 17, 2021 Approved
Chromium Snapshots 97.0.4672.0-snapshots 13 Saturday, October 16, 2021 Approved
Chromium Snapshots 97.0.4671.0-snapshots 36 Friday, October 15, 2021 Approved
Chromium Snapshots 97.0.4670.0-snapshots 31 Thursday, October 14, 2021 Approved
Chromium Snapshots 97.0.4669.0-snapshots 32 Wednesday, October 13, 2021 Approved
Chromium Snapshots 97.0.4668.0-snapshots 22 Tuesday, October 12, 2021 Approved
Chromium Snapshots 97.0.4667.0-snapshots 34 Monday, October 11, 2021 Approved
Discussion for the Chromium Snapshots Package

Ground Rules:

  • This discussion is only about Chromium Snapshots and the Chromium Snapshots package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Chromium Snapshots, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus