Repository navigation
release: publish npm API package 1.8.0 - #1985
Merged
Merged
Conversation
Require stable extension 1.42.0 now that the shared API sources have shipped and provenance validation passes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 7992926e-a6ef-49ad-b6c9-120b52c0de51
Eduardo Villalpando Mello (edvilme)
requested a review
from Stella Huang (StellaHuang95)
November 4, 2026 23:17
Eduardo Villalpando Mello (edvilme)
enabled auto-merge (squash)
November 4, 2026 23:17
Contributor
|
🔒 Automated review in progress — Stella Huang (@StellaHuang95) is auto-reviewing this PR. |
Stella Huang (StellaHuang95)
approved these changes
Nov 4, 2026
Rich Chiodo (rchiodo)
approved these changes
Nov 5, 2026
Rich Chiodo (rchiodo)
left a comment
Contributor
There was a problem hiding this comment.
Approved via Review Center.
Eduardo Villalpando Mello (edvilme)
merged commit Nov 5, 2026
ebb7d76
into
main
162 of 165 checks passed
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.
Summary
@vscode/python-environments1.8.0 and synchronize the API package lockfile.minimumExtensionVersionto 1.42.0, the newly published latest stable extension release, and record the requirement in the existing 1.8.0 changelog entry.Release readiness
The previous npm publication blocker is resolved: the provenance check passes for all five original and staged shared API sources against stable v1.42.0. npm currently lists versions 1.0.0, 1.3.0, and 1.4.0, so 1.8.0 is available for publication.
The official DevDiv pipeline 27973 (
vscode-python-environments-api,build/azure-pipeline.npm.yml) is enabled. Squash-merging this stable package-version change into main automatically triggers the build and publication process, including MicroBuild approval. This PR authorizes that npm release; nothing has been published locally or manually queued.Validation
npm --prefix api cinpm --prefix api run compilenpm --prefix api run check:release -- --provenance: passed against v1.42.0npm --prefix api test: 6 release-validation tests plus packed ESM/CommonJS runtime and modern/legacy TypeScript consumer checks passednpm --prefix api run check:release -- --artifact <1.8.0 tarball>: packed baseline revalidatednpm run lintnpm run compile-testsnpm run unittest -- --reporter dot: 3,511 passing, 9 pendinggit diff --checkGenerated sources and package artifacts are not committed. After pipeline approval/completion, verify npm
latestpoints to 1.8.0 and the published package declaresminimumExtensionVersion: 1.42.0.