Bump heroku_hatchet from 7.3.4 to 8.0.0

[dependabot]

Bumps heroku_hatchet from 7.3.4 to 8.0.0.

Changelog

Sourced from heroku_hatchet's changelog.

8.0.0

• Breaking change: Delete apps on teardown. Previously hatchet would delete apps lazily to help with debugging. This behavior allowed developers to inspect logs and heroku run bash in the event of an unexpected failure. In practice, it is rarely needed and causes accounts to retain apps indefinitely. Previously there was no cost to retaining applications, but now basic applications incur a charge. Change details:
  • The application teardown process now deletes applications directly.
  • To skip destroying applications on teardown, set HEROKU_DEBUG_EXPENSIVE=1. This env var will cause App#teardown! to skip deletion so you can introspect why one failed.
  • When hatchet needs a new application, it will first delete all applications that are created at least HATCHET_ALIVE_TTL_MINUTES ago. If it cannot delete any applications and the account is already at HATCHET_APP_LIMIT, it will sleep and try again later.
  • Introduce --older-than flag to hatchet destroy CLI command. For example, the command hatchet destroy --older-than=7will remove any apps older than the provided value (in minutes).
• Add support for GitHub Actions env vars (heroku/hatchet#189)

7.4.0

• Supports "basic" scaledown (heroku/hatchet#193)
• Breaking: Support for Ruby 2.2 is soft removed going forward only Ruby versions on the currently released stack will be supported
• Bugfix: heroku run calls are now properly rate throttled and retried heroku/hatchet#187

Commits

• 411b462 Fix bug #196 && prepare v8.0.0 release (#197)
• d0a96b0 Change App#teardown! to delete apps immediately (#195)
• a9d3dc5 Add branch detection for more CI providers (#189)
• af206b8 v7.4.0 (#194)
• 96435d6 scale to size 'basic' in App.teardown! (#193)
• f4d89ab Fix Github Action CI workflow (#192)
• e6021e8 Convert heroku/hatchet to GitHub Actions (#190)
• 7aa774b Use Next-generation convenience images in CI [changelog skip] (#178)
• 6c37340 [close #156] Capture stderr from heroku run (#187)
• d737fe0 v7.3.4 (#185)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)