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.
With the new extension release, we need to find a way to reach our userbase to make them switch to the new publisher extension.
One way to do it, would be to publish a version that open a page explaining the user that he need to replace the extension to have latest features.
I start to dig how to implement that, (as bookmark, or gitlens do), and end up on vscode extensions samples.
So far, the current version will open the Upgrade page at start.
This is still beta and prototypal, focused on the mecanism rather than the message
Once working this would need to be backport on original extension, and a release with the original publisher should be made
We'll could later use that mecanism to publicize new features.
Feedback are more than welcome!!, I wanna know what you think about this :)
🦄