Downloads of v 5.6.8:


Last Update:

21 Dec 2016

Package Maintainer(s):

Software Author(s):

  • Heroku


heroku-cli heroku cli paas cloud web webapps admin

Heroku Command Line Interface (CLI) (Install)

This is not the latest version of Heroku Command Line Interface (CLI) (Install) available.

5.6.8 | Updated: 21 Dec 2016



Downloads of v 5.6.8:



Software Author(s):

  • Heroku

Heroku Command Line Interface (CLI) (Install) 5.6.8

This is not the latest version of Heroku Command Line Interface (CLI) (Install) available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


To install Heroku Command Line Interface (CLI) (Install), run the following command from the command line or from PowerShell:


To upgrade Heroku Command Line Interface (CLI) (Install), run the following command from the command line or from PowerShell:


To uninstall Heroku Command Line Interface (CLI) (Install), 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 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

4. Choose your deployment method:

choco upgrade heroku-cli -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 heroku-cli -y --source="'STEP 3 URL'"

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

Exit $exitCode

- name: Ensure heroku-cli installed
    name: heroku-cli
    state: present
    version: 5.6.8
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'heroku-cli' do
  action    :install
  version  '5.6.8'
  source   'STEP 3 URL'

See docs at

    Name: heroku-cli,
    Version: 5.6.8,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller heroku-cli
   Name     = 'heroku-cli'
   Ensure   = 'Present'
   Version  = '5.6.8'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'heroku-cli':
  provider => 'chocolatey',
  ensure   => '5.6.8',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install heroku-cli version="5.6.8" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator espoelstra on 23 Dec 2016.


This software requires a Heroku account in order to work.

Heroku lets you deploy, run and manage applications written in Ruby, Node.js, Java, Python, Clojure, Scala, Go and PHP.

An application is a collection of source code written in one of these languages, perhaps a framework, and some dependency description that instructs a build system as to which additional dependencies are needed in order to build and run the application.

Dependency mechanisms vary across languages: in Ruby you use a Gemfile, in Python a requirements.txt, in Node.js a package.json, in Java a pom.xml and so on.

The source code for your application, together with the dependency file, should provide enough information for the Heroku platform to build your application, to produce something that can be executed.

$ErrorActionPreference = 'Stop';
$packageName = 'heroku-cli'

#First need to uninstall old toolbelt pkg if installed
$softwareName = 'Heroku Toolbelt*'
$installerType = 'EXE' 
$validExitCodes = @(0)
$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $softwareName

if ($key.Count -eq 1) {
  $key | % { 
    $file = "$($_.UninstallString)"

    Uninstall-ChocolateyPackage -PackageName $packageName `
                                -FileType $installerType `
                                -SilentArgs "$silentArgs" `
                                -ValidExitCodes $validExitCodes `
                                -File "$file"
# Remove heroku config file as requested
Remove-Item $env:USERPROFILE\.config\heroku -Recurse -ErrorAction SilentlyContinue -Force

$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url32      = ''
$url64      = ''
$checksum32 = '8e533dca6b3516626da5147ce46ccc2f61aac65e44c0df6fc8251336e4f39861'
$checksum64 = 'dc84d9d737e764748a9175745e56cee4ee3ada9a25e0b83d452d014f656489db'

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  fileType      = 'EXE'
  url           = $url32
  url64bit      = $url64

  softwareName  = 'Heroku CLI*'

  checksum      = $checksum32
  checksumType  = 'sha256'
  checksum64    = $checksum64
  checksumType64= 'sha256'
  silentArgs   = '/S'
  validExitCodes= @(0)

Install-ChocolateyPackage @packageArgs
$ErrorActionPreference = 'Stop';

$packageName = 'heroku-cli'
$softwareName = 'Heroku CLI*'
$installerType = 'EXE' 
$silentArgs = '/S'
$validExitCodes = @(0)

$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $softwareName

if ($key.Count -eq 1) {
  $key | % { 
    $file = "$($_.UninstallString)"

    Uninstall-ChocolateyPackage -PackageName $packageName `
                                -FileType $installerType `
                                -SilentArgs "$silentArgs" `
                                -ValidExitCodes $validExitCodes `
                                -File "$file"
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$key.Count matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $_.DisplayName"}
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
1. Download installer:


2. You can use one of the following methods to obtain the checksum: 
    - Use powershell function 'Get-FileHash'
    - Use Chocolatey utility 'checksum.exe'

    checksum32: 8e533dca6b3516626da5147ce46ccc2f61aac65e44c0df6fc8251336e4f39861
    checksum64: dc84d9d737e764748a9175745e56cee4ee3ada9a25e0b83d452d014f656489db

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
Heroku Command Line Interface (CLI) (Install) 340 Wednesday, October 14, 2020 Approved
Heroku Command Line Interface (CLI) (Install) 355 Thursday, October 8, 2020 Approved
Heroku Command Line Interface (CLI) (Install) 320 Friday, October 2, 2020 Approved
Heroku Command Line Interface (CLI) (Install) 169 Thursday, October 1, 2020 Approved
Heroku Command Line Interface (CLI) (Install) 352 Wednesday, September 23, 2020 Approved
Heroku Command Line Interface (CLI) (Install) 165 Tuesday, September 22, 2020 Approved
Heroku Command Line Interface (CLI) (Install) 298 Wednesday, September 16, 2020 Approved
Heroku Command Line Interface (CLI) (Install) 587 Thursday, August 27, 2020 Approved

    • git (≥ 2.8)
Discussion for the Heroku Command Line Interface (CLI) (Install) Package

Ground Rules:

  • This discussion is only about Heroku Command Line Interface (CLI) (Install) and the Heroku Command Line Interface (CLI) (Install) 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 Heroku Command Line Interface (CLI) (Install), 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