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.
While #13 fixed the crates.io release for version 0.1.1, trying to run
vsce publish
from withineditors/code
now gives this error:This PR attempts to fix that for version 0.1.2, now that I know that I can apparently run
vsce package
somewhat analogously tocargo publish --dry-run
.When I published v0.0.1 of the VS Code extension, I used this sequence of commands:
The specific
--baseImagesUrl
I passed is incorrect, but it does seem to be necessary since I use relative links ineditors/code/README.md
. However, apparently the change toeditors/code/README.md
actually broke this approach, because currently, the above error message even occurs when passing--baseImagesUrl
. This PR corrects the problem by changing thehello.png
link back to the way it was, and also fixes the link for Quench itself.The sequence of commands for publishing version 0.1.2 of the VS Code extension should look like this: