Bump to 0.2.0 and document the user-visible changes - #29
Open
Chirag6722 wants to merge 1 commit into
Open
Conversation
package.json still said 0.1.1 while main had collected a new feature and two changes to what a user sees, so anyone installing a build from main had no way to tell it apart from the released version. Minor rather than patch: "Copy as Markdown" is new surface, not a fix. README gains the three things that changed underneath it: - Copy as Markdown was shipped but never documented, so the only way to find it was to right-click and notice. - Failures Only now lists non-zero exits only. An unknown exit code used to appear there, which said the opposite of the grey "unknown" icon on the same row. - A command whose terminal is closed mid-run now leaves an unknown row where it previously left nothing at all. Worth stating plainly in Known limitations, since "no exit code was ever reported" is a real limitation and the row deserves an explanation rather than looking like a bug. Also fixes the install example, which still named truthlog-0.1.1.vsix. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
The version bump you asked for, plus the README lines that go with it.
package.jsonstill said0.1.1whilemainhad picked up a new feature and two changes to what a user actually sees, so a build frommainwas indistinguishable from the released version. Minor rather than patch, since Copy as Markdown is new surface rather than a fix.README
Three things changed underneath the docs:
That last one I put in Known limitations rather than in the feature list, because from the user's side it reads as a limitation: no exit code was ever reported and TruthLog is saying so. Without a line explaining it, a grey row appearing where nothing used to appear looks like a bug rather than the fix it is.
Also corrects the install example, which still named
truthlog-0.1.1.vsix.Not included, tell me if you want it
I did not add a
CHANGELOG.md. The Marketplace renders one as its own tab and this release has enough in it to be worth reading, but you asked for a version bump and a README note, and inventing a release-notes format for your extension seemed like your call rather than mine. Say the word and it is a small PR.One ordering note: this bumps to
0.2.0on the assumption the four issue fixes (#25, #26, #27, #28) land in the same release. If any of them slip, the number is still right, since #22 alone justifies the minor.