New version of faraday_middleware (1.0.0) produced dependency conflicts#15
Closed
depfu[bot] wants to merge 1 commit intomasterfrom
Closed
New version of faraday_middleware (1.0.0) produced dependency conflicts#15depfu[bot] wants to merge 1 commit intomasterfrom
depfu[bot] wants to merge 1 commit intomasterfrom
Conversation
Contributor
Author
|
Closed in favor of #26. |
This file contains hidden or 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
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 tried to upgrade a dependency and got errors running Bundler. It looks like there is a version conflict between two or more dependencies. Depfu doesn't try to solve these, as this would mean to update more than one dependency at a time.
Please take a look at the exact failure to figure out if this is something you need to work on.
The bundler error message was:
What changed?
✳️ faraday_middleware (~> 0.12 → ~> 1.0) · Repo · Changelog
Release Notes
1.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 51 commits:
Update publish.ymlVersion bump to 1.0.0Use Rake >= 12.3.3, securitychore: Drop commented-out codeSet version to 1.0.0.rc1README: Remove mention of old Faradays [ci skip][docs] method_override explained[docs] Gzip middleware: drop old version mentionsImport wiki pages as MarkdownPsych is default YAML Engine since Ruby 1.9.3Simplifies specs require.Split error class to its own file (#247)Faraday::Utils.(build|parse)_nested_query is definedUse default SimpleCov.formatter:cop: Style/WhileUntilModifierAvoid String#chrFix Style/IfUnlessModifier copFix Layout/LineLength cop (#238)chore: Promote cop Style/AccessModifierDeclarations to rule, for 1 exclude (#235)Avoid checking for encodingchore: RuboCop lint Style/CaseEqualitychore: RuboCop-allow middleware for Marshal to Marshal#loadchore: Style/FormatString, Style/FormatStringTokenchore: Exclude 1 instance of Naming/PredicateFix Lint/AssignmentInCondition copchore: RuboCop lint Style/StructInheritanceFix Style/MultilineTernaryOperatorchore: Update RuboCop TODO fileFix Naming/ConstantName copFix Style/NumericPredicate copFix Style/GuardClause cop warningsFix Naming/VariableNumber copFix Lint/Loop copRubocop auto correct (#220)Add GitHub Actions, remove Travis CI (#202)Fix Layout/FirstArgumentIndentation cop (#219)Fix Layout/EmptyLinesAroundClassBody cop (#218)Fix Layout/SpaceInsideBlockBraces (#217)gemspec: Support Ruby 2.3+ (#216)Fix Layout/ElseAlignment copFix Layout/EmptyLineBetweenDefsFix Layout/EmptyLineAfterMagicCommentAdd spaces after commasFix rubocop empty line after guard clausechore: RuboCop lint Layout/BlockEndNewlinechore: RuboCop lint Layout/ArrayAlignmentchore: RuboCop lint Layout/ArgumentAlignmentRuboCop: only Style/StringLiteralschore: RuboCop lint Bundler/OrderedGemsCI: Add 2.7Update to faraday 1.0 (#196)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