Lock plist to 3.x #779
Merged
Lock plist to 3.x #779
Conversation
This file contains 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
Both 3.1 and 3.2 seem to work. Currently Chef is pinned to 3.1.x, so I set the pin there to avoid conflict with Chef.
|
👍 |
|
Any reason not to pin to 3.2 and bump chef? |
|
I just didn't want any intermediate builds to fail when eventually bundler's solver will pull in the latest and do the right thing |
|
Works for me 👍 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Both 3.1 and 3.2 seem to work. Currently Chef is pinned to 3.1.x, so I
set the pin there to avoid conflict with Chef.