Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

heroku pipelines:diff command stopped working recently #3152

Closed
schpet opened this issue Dec 18, 2024 · 6 comments
Closed

heroku pipelines:diff command stopped working recently #3152

schpet opened this issue Dec 18, 2024 · 6 comments

Comments

@schpet
Copy link

schpet commented Dec 18, 2024

whenever i run heroku pipelines:diff i get this error:

Error: No release was found for $appname, unable to diff

2024-12-18 at 09 43 18@2x

this is happening on multiple apps, some on heroku-24 others on heroku-20 stack. the command used to work up until a few days ago. i can still get this info (e.g. the github diff url) through the heroku web ui for the pipeline.

heroku cli version: heroku/10.0.0 darwin-arm64 node-v20.17.0

@schpet schpet changed the title heroku pipelines:diff command stopped working recently heroku pipelines:diff command stopped working recently Dec 18, 2024
@k80bowman
Copy link
Contributor

Thank you for letting us know. We are currently evaluating a fix for this issue.

@k80bowman
Copy link
Contributor

We just released v10.0.1 which should fix this issue for you. Thank you for your patience.

@schpet
Copy link
Author

schpet commented Jan 7, 2025

@k80bowman i'm still seeing this:

❯ heroku --version
heroku/10.0.1 darwin-arm64 node-v20.17.0
❯ heroku pipelines:diff -r staging
Fetching apps from pipeline... done
Fetching release info for all apps... done
 ›   Error: No release was found for redacted-staging, unable to diff

tried on multiple apps (note: haven't deployed any of them during this QA test but they still show this info in the web ui)

@k80bowman
Copy link
Contributor

🤔 ok, thank you for the update. We'll look into it.

@k80bowman
Copy link
Contributor

k80bowman commented Jan 9, 2025

@schpet we just released v10.0.2 which has a fix that I believe should take care of this issue.

@schpet
Copy link
Author

schpet commented Jan 9, 2025

@k80bowman yep working for me! thanks so much.

@schpet schpet closed this as completed Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants