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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ cucumber (~> 5 → ~> 6) · Repo · Changelog
Release Notes
6.1.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 19 commits:
Release v6.1.0
Fix dry run with messages (#1540)
Remove deep clone of step arguments (#1538)
Revert "Add support for message formatters with dry runs (#1537)" (#1539)
Add support for message formatters with dry runs (#1537)
Fix 'attach' when passing null byte in the data (#1536)
Replace with in some places
Report empty scenarios with the json formatter (#1533)
Tell older bundlers which default branch to use
Modernise calls to bundler
Whitespace
Try adding a cache version so I can reset it
Rename master to main
Merge pull request #1528 from cucumber/undeprecate-json-formatter
Update CLI help message
Remove deprecation for the JSON formatter
Merge pull request #1527 from jmoglesby/patch-1
Switch first line back to original
Clarify removal of `puts` in CHANGELOG
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