Skip to content

Get rid of vscode-engineering template in the npm publish pipeline#1328

Merged
StellaHuang95 merged 1 commit intomicrosoft:mainfrom
StellaHuang95:npmPackage
Mar 6, 2026
Merged

Get rid of vscode-engineering template in the npm publish pipeline#1328
StellaHuang95 merged 1 commit intomicrosoft:mainfrom
StellaHuang95:npmPackage

Conversation

@StellaHuang95
Copy link
Contributor

It's been a disaster trying to get the pipeline running from a different org. I keep running into service connection and permission issues, fixing one just reveals two more. At this point it doesn't seem feasible to use the vscode-engineering template from another org.

I looked at some other pipelines we migrated for extensions like pylint, and they dropped the template and just run the raw jobs for npm pack and publishing. I'm going to try the same approach for this extension.

@@ -1,19 +0,0 @@
parameters:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

r you sure we're supposed to delete these?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added these before, it's part of using the template.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They can be removed as I am no longer using the template

@StellaHuang95 StellaHuang95 merged commit b837aa1 into microsoft:main Mar 6, 2026
44 checks passed
eleanorjboyd added a commit to eleanorjboyd/vscode-python-environments that referenced this pull request Mar 6, 2026
eleanorjboyd added a commit that referenced this pull request Mar 6, 2026
This PR reverts the following two commits from `release/1.22`

- Revert `b837aa1` - Get rid of vscode-engineering template in the npm
publish pipeline (#1328)
- Revert `d747327` - Add @vscode/python-environments npm package
(#1317)\n\nThese changes are not intended for the 1.22 release.

for increased stability for the release
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants