Outdated Heroku CI example

Question

MikeMcC399 opened this issue a year ago · comments

The five year old Heroku CI example is outdated. It specifies:

"stack": "cedar-14" (based on Ubuntu 14.04 LTS) which reached an (extended) end-of-life on Nov 2, 2020 according to Heroku documentation. The current stack is Heroku-22 based on Ubuntu 22.04
buildpacks / "https://github.com/heroku/heroku-buildpack-xvfb-google-chrome" refers to an archived repo which states that it is only supported on Cedar-14, so it is by implication also unsupported. It refers instead to https://github.com/heroku/heroku-buildpack-google-chrome.

Suggestion

Either

Remove all references to Heroku CI in the repo OR
Update the workflow to use currently-supported versions of Heroku's components, test and republish

https://devcenter.heroku.com/categories/continuous-integration
https://www.heroku.com/pricing does not appear to include a free-of-charge option (Each CI-enabled pipeline is $10/month (prorated to the second))

Mike McCready · Answer 1 · Thu May 25 2023 17:34:42 GMT+0800 (China Standard Time)

I can submit a PR to remove Heroku if that is desired.

I will not offer to update the Heroku CI and test it though. That is out of scope of what I could provide.

Mike McCready · Answer 2 · Thu May 25 2023 19:28:51 GMT+0800 (China Standard Time)

Mike McCready · Answer 3 · Fri May 26 2023 15:32:16 GMT+0800 (China Standard Time)

After reviewing #324 it seems that there could be major obstacles to getting Heroku CI working, so I have submitted PR #682 to remove the references to it. This seems like the cleanest and most efficient solution. There are enough alternate CI providers already covered.

Cypress App · Answer 4 · Tue Sep 12 2023 01:36:29 GMT+0800 (China Standard Time)

🎉 This issue has been resolved in version 2.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀