Package Details: heroku-cli 7.42.6-1

Git Clone URL: (read-only, click to copy)
Package Base: heroku-cli
Description: a tool for creating and managing Heroku apps from the command line
Upstream URL:
Licenses: custom, ISC
Conflicts: heroku-client-standalone, heroku-toolbelt, ruby-heroku
Submitter: Redrield
Maintainer: sampsoncrowley
Last Packager: sampsoncrowley
Votes: 54
Popularity: 3.45
First Submitted: 2017-08-15 23:19
Last Updated: 2020-08-13 16:15

Dependencies (3)

Required by (0)

Sources (1)

Pinned Comments

sampsoncrowley commented on 2019-12-06 05:22

Pull Requests welcome @

Latest Comments

1 2 Next › Last »

sampsoncrowley commented on 2020-06-15 17:19

Sorry for the delayed release of v7.42.1; heroku has stopped warning me when there's a new version out

sampsoncrowley commented on 2019-12-06 05:22

Pull Requests welcome @

Redrield commented on 2018-10-20 22:08

I didn't run into that when I was testing the latest release, delete ~/.cache/yay/heroku-cli and have yay pull it fresh to see if it still occurs

heppu commented on 2018-10-20 05:52

It's seem that I cannot update this anymore:

error: missing package metadata in /home/heppu/.cache/yay/heroku-cli/heroku-cli-7.17.1-1-x86_64.pkg.tar.xz

error: '/home/heppu/.cache/yay/heroku-cli/heroku-cli-7.17.1-1-x86_64.pkg.tar.xz': invalid or corrupted package

iboyperson commented on 2018-10-07 03:26

just fyi rev resets to 1 on version bump

soloturn commented on 2018-09-17 03:41

heroku has fixed versions via yarn, and "yarn add" should be possible. also new npm recommends "npm ci" instead of "npm install" to use fixed versions. would be great if the heroku package would do this instead of a "npm install".

Redrield commented on 2018-09-03 19:32

I can't reproduce this starting from a fresh start from the AUR

procrastinator commented on 2018-09-03 17:31

Getting the following error from npm

npm ERR! code E404 npm ERR! 404 Not Found: heroku-client@^3.0.6

Psykar commented on 2018-08-21 02:32

Looks like you've updated the pkgrel in the PKGBUILD, but didn't update .SRCINFO

A simple mksrcinfo should fix this =)

saifazmi commented on 2018-08-20 08:26

Getting the following error in npm logs when trying to upgrade to the latest version.

194 verbose Linux 4.18.1-arch1-1-ARCH
195 verbose argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "--user" "root" "--prefix" "/home/saif/.cache/pacaur/heroku-cli/pkg/heroku-cli/usr" "heroku-7.9.3.tgz"
196 verbose node v10.9.0
197 verbose npm v6.4.0
198 error code ETARGET
199 error notarget No matching version found for @heroku-cli/plugin-addons-v5@^7.9.3
200 error notarget In most cases you or one of your dependencies are requesting
200 error notarget a package version that doesn't exist.
200 error notarget
200 error notarget It was specified as a dependency of 'heroku'
201 verbose exit [ 1, true ]