Bumping versions to catch up with published version.#136
Merged
Conversation
tknopp-ld
requested review from
charlottemorgan,
ldhenry,
monsagri and
sheldonmartin
ldhenry
approved these changes
Dec 5, 2025
Contributor
ldhenry
left a comment
ldhenry
left a comment
There was a problem hiding this comment.
Thanks, @tknopp-ld. This seems reasonable to me.
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.
VSCodes marketplace is listing our most recent version as 6.0.12. My best guess is that this was inadvertently published from a local branch.
The version our GH actions publish is pulled from the package.json definition.
This is causing some of the functionality related to the quick targeting command to fail which is only reproduceable in that 6. published version, local builds and debugging do not reproduce the issue.
Adjusting the changelog and package.json appropriately to publish a new version.
This should also cause the OpenVSIX listing (which is used by Cursor) to update to this version as well.