Update pry 0.15.0 → 0.15.2 (minor) #506
Merged
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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ pry (0.15.0 → 0.15.2) · Repo · Changelog
Release Notes
0.15.2
0.15.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 14 commits:
Merge pull request #2341 from pry/prep-for-0-15-2
Prep for v0.15.2
Merge pull request #2340 from pry/prism-not-available-version
Avoid breaking pry when prism version is not detectable
Merge pull request #2339 from pry/prep-for-0-15-1
Prep for v0.15.1 release
Merge pull request #2338 from andrehjr/prism-not-available
Avoid breaking pry when prism is not available
Merge pull request #2333 from pry/dependabot/bundler/psych-lte-5.3.0
Merge pull request #2335 from andrehjr/make-ls-config-backwards-compat
Restore pry.config.ls compatibility to previous versions as a Hash
Merge pull request #2336 from andrehjr/move-lints-together-on-ci
Move yard to lint action on Ci instead of running on every ruby version
Update psych requirement from <= 5.2.0 to <= 5.3.0
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