Outdated Heroku CI example

[MikeMcC399]

• This is a follow-on from the closed issue Remove mention of Heroku CI support #324

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

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

References

• 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))

[MikeMcC399]

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.

[MikeMcC399]

• The stale open issue Cypress with Heroku CI cypress#4666 is also related

[MikeMcC399]

• After reviewing Remove mention of Heroku CI support #324 it seems that there could be major obstacles to getting Heroku CI working, so I have submitted PR docs: remove non-working heroku ci documentation-only workflows #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-bot]

🎉 This issue has been resolved in version 2.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀