1.2.0 (from changelog)

• [ENHANCEMENT] Drop support for Rubies 1.9.3, 2.0, 2.1, and 2.2
• [ENHANCEMENT] Add support for Rubies 2.5, 2.6, and 2.7
• [ENHANCEMENT] Drop support for Rails 3 and 4
• [ENHANCEMENT] Add support for Rails 5.2 and 6.0
• [ENHANCEMENT] Proxy all ENV values via CLI to the "heroku" command

Does any of this look wrong? Please let us know.

See the full diff on Github. The new version differs by 20 commits:

• Modify .travis.yml to address build config validation feedback
• Bump to version 1.2.0
• Don't use GitHub Actions for Figaro v1
• Update the .gitignore file
• Add an optional build to keep an eye on latest Rails
• Set the entire ENV (plus explicit configuration) in CLI tasks
• Bring the test suite up-to-date
• Update Rubies built in the Travis configuration
• Remove Code Climate, which is causing build failures
• Start exploring CI via GitHub Actions
• Create FUNDING.yml
• Call for help!
• Update the README's note about Spring and wrap some long lines
• Merge pull request #255 from mckenn/spring-doc
• replace unnecessary file references with dots
• Add spring configuration note to documentation
• Merge pull request #197 from varunsrin/patch-1
• Merge pull request #203 from jhubert/patch-1
• Support the -r alias for Heroku remotes
• Update README.md

1.0.1 (from changelog)

• Fix thor when thor/base and thor/group are required without thor.rb.
• Handle relative source path in create_link.

1.0.0 (from changelog)

• Drop support to Ruby 1.8 and 1.9.

• Deprecate relying on default exit_on_failure?. In preparation to make Thor commands exit when there is a failure we are deprecating defining a command without defining what behavior is expected when there is a failure.

  To fix the deprecation you need to define a class method called exit_on_failure? returning

  false if you want the current behavior or true if you want the new behavior.

• Deprecate defining an option with the default value using a different type as defined in the option.

• Allow options to be repeatable. See #674.

Does any of this look wrong? Please let us know.

See the full diff on Github. The new version differs by more commits than we can show here.

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)