-
Notifications
You must be signed in to change notification settings - Fork 520
Migrate to Deploy Box Product for release stage #5063
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
Conversation
(削除) Sooo this is annoyingly still a big TBD due to internal teams talking to each other. (削除ここまで)
Took a bit but it's sorted!
238571d
to
4e8fcd0
Compare
4e8fcd0
to
bf46818
Compare
@JustinGrote when this is done (early next week, identified some upstream bugs) we can consolidate the NPM optional dependencies back into dev dependencies and remove clean up the build a little.
bf46818
to
847e637
Compare
847e637
to
00393d0
Compare
@Copilot
Copilot
AI
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR migrates deployment for signed VS Code extensions to the new Deploy Box Product release stage using an updated OneBranch template. Key changes include:
- Adding a new "release" category and setting the release environment.
- Adjusting artifact paths and pool types for the GitHub and VS Code Marketplace publish jobs.
- Replacing the inline AzureCLI script with a dedicated vsce workflow step for publishing.
Comments suppressed due to low confidence (1)
.pipelines/vscode-powershell-Official.yml:197
- Verify that the 'preRelease' flag and the associated vsce block parameters are correctly configured to align with the new release process and prevent unintended pre-release deployments.
preRelease: $(prerelease)
00393d0
to
e47dcf7
Compare
Uh oh!
There was an error while loading. Please reload this page.
Uses a new template in OneBranch for publishing signed extensions to the VS Code marketplace.