New version of net-imap (0.4.10) broke the build

[depfu[bot]]

We've tested your project with an updated dependency and the build failed.

This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.

name	version specification	new version
net-imap	~> 0.2	0.4.10

Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.

If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)

We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of net-imap for this test run.

What changed?

✳️ net-imap (~> 0.2 → 0.4.10) · Repo

Release Notes

0.4.10

What's Changed

Fixes

• 🐛 Do not automatically freeze SearchResult by @nevans in #263
  This fixes a backwards incompatible change in v0.4.8 that affected the mail gem.
  See #262, reported by @stanley90.

Documentation

• 📚 Workaround rdoc method visibility issue by @nevans in #257
• 📚 Workaround rdoc issue with :yield: and visibility by @nevans in #258

Miscellaneous

• ⬆️ Bump actions/upload-pages-artifact from 2 to 3 by @dependabot in #256
• ⬆️ Bump actions/deploy-pages from 3 to 4 by @dependabot in #255
• Renew test certificates by @sorah in #259
• Add base64 dev dependency by @hsbt in #261
• Import sample code from ruby/ruby by @hsbt in #260

New Contributors

• @sorah made their first contribution in #259

Full Changelog: v0.4.9...v0.4.10

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

Commits

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

---

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 cancel merge

Cancels automatic merging of this PR

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