You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that following this PR, this package (@vscode/vsce, MIT licensed) now depends on @vscode/vsce-sign which is under the Microsoft license instead.
The current setup makes the licensing for @vscode/vsce land in a grey area.
Are there any plans to align the two?
Thanks.
The text was updated successfully, but these errors were encountered:
Thanks for the ping, license questions always require me to consult with our legal team which usually means that the response will take at least a couple of weeks, if not months. Thanks for your understanding.
Hi team,
I noticed that following this PR, this package (
@vscode/vsce
, MIT licensed) now depends on@vscode/vsce-sign
which is under the Microsoft license instead.The current setup makes the licensing for
@vscode/vsce
land in a grey area.Are there any plans to align the two?
Thanks.
The text was updated successfully, but these errors were encountered: