This repository was archived by the owner on Oct 11, 2022. It is now read-only.
Update draft-js-plugins-editor: 2.0.4 → 2.1.1 (minor) #3640
Conversation
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
depfu
bot
force-pushed
the
depfu/update/api/yarn/draft-js-plugins-editor-2.1.1
branch
from
e96be46 to
28a50ab
Compare
brianlovin
approved these changes
Jul 20, 2018
depfu
bot
deleted the
depfu/update/api/yarn/draft-js-plugins-editor-2.1.1
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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 updated a dependency and here is what you need to know:
Additionally, the update changed a few other dependencies as well:
You should probably take a good look at the info here and the test results before merging this pull request, of course.
What changed?
✳️ draft-js-plugins-editor (2.0.4 → 2.1.1) · Repo · Changelog
✳️ find-with-regex (1.0.2 → 1.1.3) · Repo
Sorry, we couldn't find anything useful about this release.
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.