⚠️ [fixing yanked version] Update pry: 0.14 → 0.14.1 (minor) #68
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're getting an error that the version of pry you're currently using is no longer installable, it most likely has been yanked. That means your deployment, CI build and local development setup are broken until you update pry to a different version.
We recommend to merge this update as soon as possible!
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.14 → 0.14.1) · Repo · Changelog
Release Notes
0.14.1 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 9 commits:
Merge pull request #2183 from pry/release-0-14-1
Release v0.14.1
CHANGELOG: update with current changes
Merge pull request #2180 from wenderjean/fix/deprecate-plugins-cli-option
Merge pull request #2182 from pry/2181-doc-formatting-fix
helpers/documentation: don't colorize twice
Merge pull request #2158 from andrehjr/fix-color-off-overwrite
Merge pull request #2154 from xjunior/patch-1
Deprecate the option "--plugins" on CLI considering PluginManager does not exist anymore
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