[Doppins] Upgrade dependencies #1
Open
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
|
well @doppins-bot, you've made self conflicting PRs |
|
Sorry for the late answer @graingert, I've been on vacation. I'll look into it, but in specifically this case I think it might have been because #2 was merged before this? |
|
@ekmartin it would be nice for @doppins-bot to automatically replace these commit with new ones based on master |
|
Hm, I guess that might be a possibility yes. Currently we only update pull requests for single dependency upgrades, such as #3, and then only if a new version of that specific dependency is released. Example: ekmartin/slack-irc#89 (comment) |
|
@ekmartin is there a "rebase" command for @doppins-bot ? |
|
No, sorry. Not at the moment at least. |
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, and thank you for trying out Doppins.
This initial pull request upgrades all your dependency ranges to the latest
available version. From now on any new dependency releases will result in a pull
request to your repository, submitted in real-time.
Make sure that it doesn't break anything, and happy merging!
The upgraded dependencies are:
==1.9b1to==1.9==2.4.2to==2.5.0