Skip to content

build: prepare stable extension release 1.42.0 - #1981

Merged
Eduardo Villalpando Mello (edvilme) merged 1 commit into
mainfrom
release/prep-1.42.0
Nov 4, 2026
Merged

Eduardo Villalpando Mello (edvilme) merged 1 commit into
mainfrom
release/prep-1.42.0

Conversation

@edvilme

Copy link
Copy Markdown
Contributor

Summary

  • Prepare stable extension version 1.42.0 in package.json and package-lock.json; no implementation or npm package metadata changes.
  • Follow docs/releasing.md: after this PR merges, cut release/1.42.0 from the merged commit, then advance main to 1.43.0 in a separate PR.
  • This stable extension release is required before the npm package can publish the shared API changes currently on main.

Validation

  • npm run lint
  • npm run compile-tests
  • npm run unittest -- --reporter dot: 3,496 passing, 9 pending
  • npm run package
  • npm run smoke-test: 31 passing, 1 pending
  • npm run e2e-test: 4 passing
  • git diff --check

Unit, production-build, smoke and E2E checks used the pipeline's Node 22.21.1. Smoke/E2E checks used the PET Windows artifact from Monaco build 448722, matching the configured release/2026.12 dependency.

Publication

Publication is authorized by the maintainer's release request, but has not been queued yet. The enabled official stable definition is Monaco pipeline 615, backed by build/azure-pipeline.stable.yml; DevDiv pipeline 28768 is disabled and was not changed. Queue the Monaco pipeline on the prepared stable branch with publishExtension=true, then verify Marketplace publication and the generated GitHub tag/release before releasing npm.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 7992926e-a6ef-49ad-b6c9-120b52c0de51
@StellaHuang95

Stella Huang (StellaHuang95) commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

🔒 Automated review in progress — Stella Huang (@StellaHuang95) is auto-reviewing this PR.

@StellaHuang95

Copy link
Copy Markdown
Contributor

Result: 🔴 could-not-verify

Verification details

Verification: Automated verification is best effort. The PR author remains responsible for testing.

Summary: [unavailable] Container verification could not start and local execution was not authorized for this PR HEAD: Podman CLI is not installed or is not on PATH.

Test runs: none recorded.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Approved via Review Center.

@StellaHuang95 Stella Huang (StellaHuang95) added the review-auto:approved Automated review: no blocking findings (approval posted). label Nov 4, 2026

@bschnurr Bill Schnurr (bschnurr) left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Approved via Review Center.

@edvilme
Eduardo Villalpando Mello (edvilme) merged commit 86b00d1 into main Nov 4, 2026
161 of 165 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bump for the release Release bump PR no-changelog no-merge PR is currently blocked from merging review-auto:approved Automated review: no blocking findings (approval posted).

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants