Update dry-configurable to version ~> 1.0#73
Open
frostmark wants to merge 1 commit intosouthbridgeio:masterfrom
Open
Update dry-configurable to version ~> 1.0#73frostmark wants to merge 1 commit intosouthbridgeio:masterfrom
frostmark wants to merge 1 commit intosouthbridgeio:masterfrom
Conversation
Contributor
|
Thank you. We have plans to update to the latest version of telegram-bot-ruby in our project. After the update, we will definitely apply your corrections. Now we have slightly different directions of development |
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.
Hi! 👋
I ran into a compatibility issue when using this gem alongside
telegram-bot-ruby. The conflict is caused by the version ofdry-configurablebeing locked below1.0.bundle Fetching gem metadata from https://rubygems.org/......... Resolving dependencies... Could not find compatible versions Because dry-configurable >= 0.12.0, < 0.13.0 depends on dry-core >= 0.5, < 1.A and dry-configurable >= 0.8.0, < 0.12.0 depends on dry-core >= 0.4.7, < 1.A, dry-configurable >= 0.8.0, < 0.13.0 requires dry-core >= 0.4.7, < 1.A. And because tdlib-ruby >= 2.2.0, < 3.1.0 depends on dry-configurable ~> 0.9, tdlib-ruby >= 2.2.0, < 3.1.0 requires dry-core >= 0.4.7, < 1.A or dry-configurable >= 0.13.0, < 1.A. (1) So, because tdlib-ruby >= 3.1.0 depends on dry-configurable ~> 0.13 and dry-configurable >= 0.13.0, < 1.0.0 depends on dry-core ~> 0.6, tdlib-ruby >= 2.2.0 requires dry-core >= 0.4.7, < 1.A. Because dry-struct >= 1.6.0, < 1.7.0 depends on dry-types >= 1.7, < 2 and telegram-bot-ruby >= 1.0.0.pre depends on dry-struct ~> 1.6, telegram-bot-ruby >= 1.0.0.pre requires dry-types >= 1.7, < 2 or dry-struct >= 1.7.0, < 2.A. And because dry-types >= 1.7.0 depends on dry-core ~> 1.0 and dry-struct >= 1.7.0 depends on dry-core ~> 1.1, telegram-bot-ruby >= 1.0.0.pre requires dry-core >= 1.0, < 2.A. And because tdlib-ruby >= 2.2.0 requires dry-core >= 0.4.7, < 1.A (1), tdlib-ruby >= 2.2.0 is incompatible with telegram-bot-ruby >= 1.0.0.pre. So, because Gemfile depends on telegram-bot-ruby ~> 2.1 and Gemfile depends on tdlib-ruby ~> 3.0, version solving has failed.This PR updates the dependency to
~> 1.0, which resolves the issue and should remain compatible with existing functionality.Let me know if you'd like me to make any adjustments — happy to update the PR if needed.
Thanks again for your work on this gem!