Update launchy: 2.5.0 → 2.5.2 (patch)

[depfu]

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

What changed?

↗️ launchy (indirect, 2.5.0 → 2.5.2) · Repo · Changelog

Release Notes

2.5.2 (from changelog)

• Update Addressable - #145 - JamieKDonnelly
• Fix deprecated usage of Object#=~ - #138 - marcrohloff
• Move to sempahore for matrix builds and macos tests

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

Commits

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

• Release 2.5.2
• update releast task to switch use main branch
• remove 2.5.9 from the test matrix
• revert removing the ruby-build update for macos builds
• bump macos build image
• force at least bundler version to 2.4.1
• regenerate spec with new version
• update history for release
• update bundled with version
• Merge pull request #138 from marcrohloff/fix-for-deprectated-object-match
• bump mac osx build matrix
• fix truffle ruby versions
• update ruby version matrix
• parallelize platform builds
• remove .ruby-versino
• update ruby on macos builds
• start updating history
• bump version
• remove jruby from macos testing
• test on macos
• turn off github workflows
• add ruby 2.5 to semaphore...
• bump dependencies
• add gemfile.lock to repo
• force build
• update badge url
• switch to semaphore
• downrev simplecov to allow for ruby 2.3
• remove debug env
• regenerate gemspec
• seeing if ruby 2.3 still works
• set debug to true for test
• stub the method and make sure it is called
• drop head and debug ruby versions
• regenerate gemspec
• bump launchy version
• reduce ruby matrix
• fix workflow syntax
• fix workflow syntax
• adding github workflow
• update addressable to 2.8
• Fix the error "warning: deprecated Object#=~ is called on Launchy::Argv; it always returns nil" when `browser_cmdline` is an Argv instance
• Update urls to be https instead of http as approproriate
• Merge pull request #134 from piruty/fix_typo_in_readme
• fix a small typo in README.md

---

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)