GeezerVison

build: prepare stable extension release 1.42.0

Co-authored-by: Copilot <[email protected]>

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

Release 1.40: rebase release history onto main (#1933)

## Summary

Bring every change from `main` through
`9f1e63d152ead34491a4e3ddffd934a0fece839e` into `release/1.40`, while
retaining the stable extension version `1.40.0`.

## History

- Rebase the existing `release/1.40` history onto `main`; do not squash
or selectively cherry-pick the main commits.
- Preserve all 29 main-only commits with their original commit IDs.
- Replay the two release-only version commits with their original
authors and messages:
  - `11b8e83a` -> `61aeb25b`: bump extension version to `1.39.1`.
  - `e7d90fa0` -> `e6a89ad2`: bump extension version to `1.40.0`.
- Resolve only the version conflicts in `package.json` and
`package-lock.json`.
- The final tree is identical to the selected main commit except for the
three extension-version fields, which are `1.40.0`.

Use a merge commit when merging this PR to preserve the existing main
commit IDs. Squash merging or GitHub's rebase-and-merge would not
preserve that ancestry. The existing release branch has not been
force-pushed.

## Validation

- `npm run lint`
- `npm run compile-tests`
- `npm run unittest -- --reporter dot`: 2,885 passing, 9 pending.
- `npm run package`
- `git diff --check`
- Verified main is an ancestor of this branch, and `git range-diff`
retains both release-only commits.
- Verified the rebased tree matches the validated main-based `1.40.0`
tree.

## Release coordination

- This PR includes all main changes, including new features and API
changes, rather than only the previously proposed fixes.
- `main` remains at `1.41.0`; no follow-up development-version bump is
currently necessary.
- No release pipeline has been manually triggered and no publication has
been authorized.
- Before merging, confirm the active stable pipeline: the DevDiv stable
definition triggers on `release/*` pushes and defaults publishing to
enabled behind a manual validation gate.

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Eleanor Boyd <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Karthik Nadig <[email protected]>
Co-authored-by: Stella Huang <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Bill Schnurr <[email protected]>
Co-authored-by: Copilot Autofix powered by AI <[email protected]>
Copilot-Session: ce6aeb0a-6210-4716-8a84-2f3e7555625f

build: bump extension version to 1.38.0 (#1808)

## Summary
- Bump the Python Environments extension version from 1.37.0 to 1.38.0.
- Refresh the root npm lockfile with `npm i`.

Co-authored-by: Copilot <[email protected]>

Bump version to 1.36.0 for release (#1595)

## Summary
- Bump the extension package version to 1.36.0.
- Refresh package-lock.json with npm.

## Notes
- After syncing to upstream/main, the stable Azure pipeline PET artifact
branch is already refs/heads/release/2026.12. The requested 2026.8 ->
2026.10 bump is therefore already superseded on main, so this PR avoids
downgrading the PET artifact branch.

## Verification
- npm install --package-lock-only

Bump version to 1.34.0 in package.json (#1576)

Bump version to 1.30.0 in package.json (#1505)

Update to PET 2026.6 (#1461)

bump version to 1.26.0 (#1411)

chore: bump version to 1.24.0 (#1386)

bump PET on release branch (#1342)