escape strings in version sub pattern#462
Merged
jimmyjames merged 1 commit intomasterfrom Oct 20, 2022
Merged
Conversation
Widcket
approved these changes
Oct 20, 2022
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When trying to perform a release with
@a0/ship, was getting an error regarding invalid JSON. I suspect this is coming from thefilesdefinition in.shiprc. The change in this PR escapes the double quote char. When attempting to run ship with this change, I did not receive a JSON parsing error, just a dirty repo error. That should mean that the JSON is valid now. Once this is merged we can try and perform the release again.