fix(ci): set workingDirectory for ADO extension pipelines#100
Merged
digitarald merged 1 commit intomainfrom Apr 1, 2026
Merged
fix(ci): set workingDirectory for ADO extension pipelines#100digitarald merged 1 commit intomainfrom
digitarald merged 1 commit intomainfrom
Conversation
The vscode-engineering templates default workingDirectory to the repo root, but this repo's extension lives in vscode-extension/. Without this parameter, vsce package reads the root package.json (which lacks engines.vscode and publisher), causing the Package Extension step to fail with 'Manifest missing field: engines'. Sets workingDirectory to $(Build.SourcesDirectory)/vscode-extension in both stable and pre-release pipeline configs.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes the Azure DevOps packaging pipelines for agentrc-vscode by ensuring the vscode-engineering extension templates run their packaging steps from the VS Code extension subdirectory (rather than the repo root), avoiding picking up the wrong package.json.
Changes:
- Set
workingDirectory: $(Build.SourcesDirectory)/vscode-extensionin the stable extension publish pipeline. - Set
workingDirectory: $(Build.SourcesDirectory)/vscode-extensionin the prerelease extension publish pipeline.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.azure-pipelines/publish-extension.yml |
Passes workingDirectory to the vscode-engineering stable extension pipeline template so packaging runs from vscode-extension/. |
.azure-pipelines/publish-extension-prerelease.yml |
Passes workingDirectory to the vscode-engineering prerelease extension pipeline template so packaging runs from vscode-extension/. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
agentrc-vscodeAzure Pipelines build has been failing on every main commit with:The
vsce packagestep runs from the repo root, picking up the rootpackage.json(@microsoft/agentrc) instead ofvscode-extension/package.json. The output filename confirms this:undefined.@microsoft/agentrc.2.1.0.universal.vsix(root name, no publisher).Fix
Both
.azure-pipelines/publish-extension.ymlandpublish-extension-prerelease.ymlnow passworkingDirectory: $(Build.SourcesDirectory)/vscode-extensionto thevscode-engineeringtemplates, sovsce packageruns from the extension directory.Verification
The
agentrc-vscode-corepipeline (which handles tests, APIScan, etc.) has been green throughout — this only affects the packaging pipeline.