- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add support for publishing platform-specific .vsix
#280
Conversation
@GitMensch and @mbehr1, I haven't started coding the feature yet, but I updated the documentation with what I have in mind. Would you mind taking a look at it, to see if the approach is acceptable? Any feedback is welcome. |
94e87d8
to
15d9f18
Compare
@felipecrs yep, useful! I'll try to migrate my workflows to that approach. |
I'll try to merge the PR in the coming days so. :) |
e0a78d7
to
f18b67c
Compare
Oh wow, this got so complicated. But it's finally coming to an end. |
.vsix
08fe52c
to
85573ac
Compare
🎉 This PR is included in version 5.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
New features
packageVsix
option can now be explicitly disabled withfalse
publishPackagePath
option was added, which allows the use of globs like*.vsix
VSCE_TARGET
Check the documentation for an example on how these new features can be combined to achieve platform-specific extensions publishing.