Downloads:

62,402

Downloads of v 7.42.13.0:

19

Last Update:

28 Aug 2020

Package Maintainer(s):

Software Author(s):

  • Heroku

Tags:

heroku-cli heroku cli paas cloud web webapps admin

Heroku Command Line Interface (CLI) (Install)

Downloads:

62,402

Downloads of v 7.42.13.0:

19

Maintainer(s):

Software Author(s):

  • Heroku

Heroku Command Line Interface (CLI) (Install)

Some Checks Have Failed or Are Not Yet Complete

1 Test Passing and 1 Failing Test


Validation Testing Passed


Verification Testing Failed

Details

This package was rejected on 05 Oct 2020. The reviewer chocolatey-ops has listed the following reason(s):

jtcmedia (maintainer) on 28 Aug 2020 03:06:42 +00:00:

User 'jtcmedia' (maintainer) submitted package.

chocolatey-ops (reviewer) on 28 Aug 2020 03:42:48 +00:00:

heroku-cli has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 29 Aug 2020 20:07:16 +00:00:

heroku-cli has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/683518b2afde9a70bd6eb74a742c9b44 for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

gep13 (reviewer) on 31 Aug 2020 06:43:49 +00:00:

Auto Verification Change - Verification tests have been set to rerun.

chocolatey-ops (reviewer) on 31 Aug 2020 18:00:57 +00:00:

heroku-cli has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/33d18611aab8714229ad0cd12d8077ba for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

chocolatey-ops (reviewer) on 20 Sep 2020 06:44:43 +00:00:

We've found heroku-cli v7.42.13.0 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:

  • Log in to the site and respond to the review comments.
  • Resubmit fixes for this version.
  • If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

chocolatey-ops (reviewer) on 05 Oct 2020 06:48:50 +00:00:

Unfortunately there has not been progress to move heroku-cli v7.42.13.0 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.

Status Change - Changed status of package from 'submitted' to 'rejected'.

Description

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.


legal\LICENSE.txt
From: https://github.com/heroku/cli/blob/master/LICENSE

LICENSE

The ISC License (ISC)

Copyright © Heroku 2017

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
legal\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
 
1. Download installer:

    x32: https://cli-assets.heroku.com/heroku-x64.exe
    x64: https://cli-assets.heroku.com/heroku-x86.exe


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

    checksum32: C1679915CB0CC0A1AF8C6C3AE5C9A18412BEB1FFDFBF285E8DF7CD53CE932A31
    checksum64: E1740BEB9AB1BF42A1B283A991E886157A15765E44CCE4ADE9CDF4FF8737082E

   Using AU:
    
    Get-RemoteChecksum https://cli-assets.heroku.com/heroku-x86.exe
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';
$packageName = 'heroku-cli'
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$installerFile = if ((Get-ProcessorBits 64) -and $env:chocolateyForceX86 -ne 'true') {
         Write-Host "Installing x64 bit version"; Get-Item "$toolsDir\*x64.exe"
} else { Write-Host "Installing x32 bit version"; Get-Item "$toolsDir\*x86.exe" }

$packageArgs = @{
  packageName   = $packageName
  fileType      = 'EXE'
  file          = $installerFile
  softwareName  = 'Heroku CLI'
  silentArgs   = '/S'
  validExitCodes= @(0)
}

Install-ChocolateyInstallPackage @packageArgs

Remove-Item ($toolsDir + '\*.' + $packageArgs.fileType)
tools\chocolateyuninstall.ps1
$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"}
}
tools\heroku-x64.exe
md5: 150A64CAE05E79F2C886C66496216E77 | sha1: B6818E226D27071D0201AE34C460EE9F8982FBBD | sha256: C1679915CB0CC0A1AF8C6C3AE5C9A18412BEB1FFDFBF285E8DF7CD53CE932A31 | sha512: 03AA0843F8B74243A54845F82D11B55E3A692222A5BB6A8B89D39FB75613F5A2591D687960D90B55EB543ED661FF9672936950F4ABCEA7357D7A412B3BBF6288
tools\heroku-x86.exe
md5: 29A255CAD27DEA0C8F2896F6150C89A4 | sha1: 70C561522C82923F5C4BBB16C4CA12E03159F9C7 | sha256: E1740BEB9AB1BF42A1B283A991E886157A15765E44CCE4ADE9CDF4FF8737082E | sha512: 7E400E8E0D8F2039048EE940B2C4FE49F4CF119A767BEB2E576389820F148DBE519B47432BF55D32341CE9AD48864162F177789E90A7A4495645BE42300FF933

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) 7.46.1.0 193 Wednesday, October 21, 2020 Approved
Heroku Command Line Interface (CLI) (Install) 7.46.0.0 342 Wednesday, October 14, 2020 Approved
Heroku Command Line Interface (CLI) (Install) 7.45.0.0 357 Thursday, October 8, 2020 Approved
Heroku Command Line Interface (CLI) (Install) 7.44.0.0 320 Friday, October 2, 2020 Approved
Heroku Command Line Interface (CLI) (Install) 7.43.3.0 169 Thursday, October 1, 2020 Approved
Heroku Command Line Interface (CLI) (Install) 7.43.2.0 352 Wednesday, September 23, 2020 Approved
Heroku Command Line Interface (CLI) (Install) 7.43.1.0 166 Tuesday, September 22, 2020 Approved
Heroku Command Line Interface (CLI) (Install) 7.43.0.0 298 Wednesday, September 16, 2020 Approved

    • git (≥ 2.8.1)
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