Skip to content

Need to sign and publish VSCode VSIX with vsce #4267

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.

Sign up for GitHub

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

Jump to bottom
Open
bwateratmsft opened this issue Aug 29, 2024 · 1 comment
Open

Need to sign and publish VSCode VSIX with vsce #4267

bwateratmsft opened this issue Aug 29, 2024 · 1 comment
Assignees
@danieljurek
Labels
engsys
Milestone
Selenium

Comments

@bwateratmsft
Copy link
Contributor

Beginning sometime in October, we will no longer be able to publish the VSCode extension as-is. We need to enable signing with vsce, as well as do publishing via vsce and workload identity federation.

/cc @danieljurek @rajeshkamal5050
@rajeshkamal5050 rajeshkamal5050 added this to the Selenium milestone Aug 29, 2024
@bwateratmsft
Copy link
Contributor Author

@alexweininger is doing this for the core Azure extensions and the Docker extension. We should look at his work.

@danieljurek danieljurek moved this from 🤔 Triage to 🐝 Dev in Azure SDK EngSys 🥧📅 Nov 4, 2024
@danieljurek danieljurek moved this from 🐝 Dev to 📋 Backlog in Azure SDK EngSys 🥧📅 Nov 4, 2024
@kurtzeborn kurtzeborn moved this from 🔬 Dev in PR to 🎊 Closed in Azure SDK EngSys 🥧📅 Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@danieljurek danieljurek

Labels
engsys
Projects
Azure SDK EngSys 🥧📅
Status: 🎊 Closed
Milestone
Selenium
Development

No branches or pull requests
3 participants
@danieljurek @rajeshkamal5050 @bwateratmsft