-
Notifications
You must be signed in to change notification settings - Fork 213
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
Support signing related features #993
Comments
* fix #993 * feedback * Update src/main.ts Co-authored-by: João Moreno <joao.moreno@microsoft.com> --------- Co-authored-by: João Moreno <joao.moreno@microsoft.com>
@sandy081 vsce needs to be published still. Installed from main for the purposes of verification. |
I'm not clear on how to generate the |
@connor4312 vsce does not support signing the manifest, one has to sign the manifest separately and pass it vsce for publishing. This is limited only feature for now. I am marking this as verified since our pipelines are successfully generating the manifest, signing it and publish them using vsce. |
Support following signing related features
vsce generate-manifest --packagePath <package-path> --out <manifest-output-path>
vsce publish --packagePath <package-path> --manifestPath <manifest-path> --signaturePath <signature-path>
The text was updated successfully, but these errors were encountered: