Skip to content

Use AzureArtifacts registry for vsce install - #732

Merged
gfs merged 3 commits into
mainfrom
gfs/FixPipelinePublishing
Mar 30, 2026
Merged

Use AzureArtifacts registry for vsce install#732
gfs merged 3 commits into
mainfrom
gfs/FixPipelinePublishing

Conversation

@gfs

@gfs gfs commented Mar 26, 2026

Copy link
Copy Markdown
Contributor

Update CI pipeline to install @vscode/vsce using the Azure Artifacts npm registry via the --registry flag. This ensures the vsce package is resolved from the organization's feed during the release pipeline.

gfs added 3 commits March 26, 2026 09:48
Update CI pipeline to install @vscode/vsce using the Azure Artifacts npm registry via the --registry flag. This ensures the vsce package is resolved from the organization's feed during the release pipeline.
Add a Changelog entry for version 1.0.77 (2026-03-26) under Pipeline describing an attempt to fix the VS Code publishing pipeline by installing the VSCE tool.
Update .vscode/settings.json to change "editor.codeActionsOnSave.source.fixAll.eslint" from true to "explicit" so ESLint auto-fixes are applied only when explicitly requested instead of running all fixes on save.

This change is automatically made by VS Code when the project is opened.
@gfs
gfs requested a review from danfiedler-msft March 26, 2026 17:27
@gfs
gfs merged commit 8dba33e into main Mar 30, 2026
19 checks passed
@gfs
gfs deleted the gfs/FixPipelinePublishing branch March 30, 2026 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants