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.
Hello lovely humans,
unexpected just published its new version 10.18.1.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As unexpected is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
The new version differs by 110 commits .
ce255c6
10.18.1
18581ad
Move greedy-interval-packer from devDependencies to dependencies, oops.
e4df713
10.18.0
0de627f
Build unexpected.js
75b0c16
Merge pull request #333 from unexpectedjs/feature/arrayMoveArrows
917723b
Avoid trailing whitespace when the first change is a moveTarget item.
b9839d8
Make sure that we render a max of 3 arrow lanes.
2110adf
Separate the packing from the arrowsAlongsideChangeOutputs style.
accb2f2
Pack using the change indices instead of the measured heights of the change outputs.
8966ca6
Update expected output in a test where the array-changes fix causes inserts and moveSources to be ordered differently (harmless).
38f0c46
Render arrow heads with ▷ instead of >
eac213a
Use greedy-interval-packer to avoid reserving too much horizontal space for the arrows.
4357884
array-like: Render moves with arrows
0738cf6
Update array-changes-async to 3.0.0 and array-changes to 2.0.0.
1c4e1dc
10.17.2
There are 110 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade