Upgrade aruba to version 1.1.2

[depfu]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ aruba (~> 0.14 → ~> 1.1) · Repo · Changelog

Release Notes

1.1.2 (from changelog)

• Add Bundler as an explicit runtime dependency (#810 by luke-hill)

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

Commits

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

• Prepare version 1.1.2 for release
• Merge pull request #819 from cucumber/improve-have-file-content-spec
• Fix specs for have_file_content matcher
• Merge pull request #815 from cucumber/improve-signal-tests
• Merge pull request #818 from cucumber/fix-cuke-timeouts-mac
• Regenerate RuboCop to-do file
• Test SpawnProcess#send_signal in specs
• Fix some cucumber timeout issues on MacOS in CI
• Merge pull request #810 from cucumber/bugfix/bundler_runtime_req
• Permit versions of 1.x bundler
• Move RSpec status persistence file out of spec directory
• Update README to make it clear GitHub Issues are for issues
• Merge pull request #812 from cucumber/remove-bundler-require
• Remove Bundler.require_relative from spec helper
• Merge pull request #811 from cucumber/use-appraisal
• Allow testing with different versions of runtime dependencies
• Bundler is a runtime dependency inside aruba/api/bundler - So require it as so
• Merge pull request #809 from cucumber/update-development-branch-references
• Make GitHub Actions run when targeting main
• Update references to master branch to main in documentation
• Merge pull request #808 from cucumber/readme-mentions-main

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Circle CI, Semaphore and Travis-CI are all excellent options.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​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)