New version of net-imap (0.4.13) broke the build #144
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
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.13) · Repo
Release Notes
0.4.13
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 28 commits:
🔖 Bump version to 0.4.13🔀 Merge pull request #299 from ruby/gemspec-ignore♻️ Use __dir__, not File.expand_path '..', __FILE__📦 Don't keep .github, .gitignore, .mailmap in gem📚 Improve rdoc for Net::IMAP.new ssl: params📚 Update rdoc for Config and related updates🔀 Merge pull request #293 from ruby/config-responses_without_block🔧 Check type for config.responses_without_block🔊 Warn about deprecated responses usage🔧 Add config option for `sasl_ir`📚 Improve Config class rdoc🔀 Merge pull request #295 from ruby/config-clean-up📚 Simplify Config defaults documentation♻️ Switch Config autoload to require_relative🔀 Merge pull request #291 from ruby/config-class🔧 Use client config for idle_response_timeout🔧 Use client config for open_timeout🔧 Use client config for debug mode🔧 Use global config for Net::IMAP.debug🔧 Add client config (currently unused)🔧🏷 Add type coercion for config attributes🔧 Add a global config object🔧 Add config inheritance🔧 Add a default config object🔧⚡️ Store Config attr_accessors in a Struct🔧 Add very basic Config class (currently unused)⬆️ Bump step-security/harden-runner from 2.8.0 to 2.8.1 (#292)📖 Improve #idle and #idle_done rdoc