-
Notifications
You must be signed in to change notification settings - Fork 0
Comparing changes
Open a pull request
base repository: grismsdn-com/vscode-python-debugger
base: main
head repository: microsoft/vscode-python-debugger
compare: main
- 19 commits
- 27 files changed
- 10 contributors
Commits on Jan 22, 2026
-
Fix publish pipeline (microsoft#933)
* pass .nmprc to publish * just always copy * temp disable store publish * try uploading npmrc * check .npmrc is a file * Remove npmrc artifact; add custom registry setup Stop publishing/downloading .npmrc as a pipeline artifact. Instead, configure npm to use a temp user config (NPM_CONFIG_USERCONFIG=$(Agent.TempDirectory)/.npmrc) and support customNPMRegistry in the shared setup template, including auth (npmAuthenticate@0) and lockfile registry rewrites. Thread $(AZURE_ARTIFACTS_FEED) through DevDiv pipeline templates to enable the custom registry flow. * Explicitly setting $env:NPM_CONFIG_REGISTRY in the “📦 Setup NPM Registry” step. Making the generated JS do const registry = process.env.NPM_CONFIG_REGISTRY; (and error if it’s missing), instead of trying to inline/concatenate a JSON-escaped registry string. * fix regex * uncomment publish * The refactor to externalize the registry setup into scripts and call them from setup.yml:22-67 (plus the new documented scripts under scripts). * prettier
Configuration menu - View commit details
-
Copy full SHA for 86a5d33 - Browse repository at this point
Copy the full SHA 86a5d33View commit details -
Remove scripts folder add logic back to yml (microsoft#935)
* remove scripts due to releaseJob * disable publish for testing * re-enable publish
Configuration menu - View commit details
-
Copy full SHA for 1b01a2c - Browse repository at this point
Copy the full SHA 1b01a2cView commit details
Commits on Jan 23, 2026
-
Bump lodash from 4.17.21 to 4.17.23 (microsoft#934)
Bumps [lodash](https://github.com/lodash/lodash) from 4.17.21 to 4.17.23. - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](lodash/lodash@4.17.21...4.17.23) --- updated-dependencies: - dependency-name: lodash dependency-version: 4.17.23 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 679f155 - Browse repository at this point
Copy the full SHA 679f155View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9e0e66c - Browse repository at this point
Copy the full SHA 9e0e66cView commit details -
Fix passing parameter enabledApiProposalsJson (microsoft#937)
* Added template parameter enabledApiProposalsJson. Added env: EnabledApiProposalsJson: ${{ parameters.enabledApiProposalsJson }} on the PowerShell@2 step. Script continues to read $env:EnabledApiProposalsJson (safe for JSON with quotes). publish-extension.yml Wired it up: enabledApiProposalsJson: $(EnabledApiProposalsJson) when calling the publish template. This should fully eliminate the PowerShell parser failure you hit while still allowing the --allow-proposed-apis ... list to be applied when present. * disable publish * The System.Object[] happened later, inside the publish step, because the publish script was turning the JSON into a nested array and then joining/printing it poorly — which then produced an invalid CLI arg: --allow-proposed-apis System.Object[]. I’ve fixed that parsing/flattening in publish.yml, so the publish log should now show: enabledApiProposals (from EnabledApiProposalsJson): portsAttributes, debugVisualization, contribViewsWelcome and the npx ... publish command should include: --allow-proposed-apis portsAttributes debugVisualization contribViewsWelcome * uncomment publishConfiguration menu - View commit details
-
Copy full SHA for f0a8a66 - Browse repository at this point
Copy the full SHA f0a8a66View commit details
Commits on Jan 26, 2026
-
Removed all --allow-proposed-apis logic (and the EnabledApiProposalsJ…
…son env wiring) from publish.yml. (microsoft#938) Updated both publish paths to use --no-verify (correct flag name; --noVerify won’t work): Pre-release: adds --no-verify --pre-release Stable: adds --no-verify This should avoid the unknown option '--allow-proposed-apis …' failure entirely by no longer passing that option.
Configuration menu - View commit details
-
Copy full SHA for a6ee0a8 - Browse repository at this point
Copy the full SHA a6ee0a8View commit details
Commits on Jan 30, 2026
-
Additional python 3.13 and 3.14 support (microsoft#940)
* Additional python 3.13 and 3.14 support - remove debugpy_info.json for DEBUGPY_VERSION in noxfile.py * ruff format -- --fix .
Configuration menu - View commit details
-
Copy full SHA for 0d8927f - Browse repository at this point
Copy the full SHA 0d8927fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 6d06928 - Browse repository at this point
Copy the full SHA 6d06928View commit details
Commits on Feb 13, 2026
-
fix: use run.executable instead of activatedRun.executable for interp…
…reter identification (microsoft#949) getInterpreterDetails, getSettingsPythonPath, and getExecutableCommand need the actual Python binary path, not the activated run command. Using activatedRun.executable breaks when environment managers set it to a wrapper command (e.g. pixi run ... python). This unblocks managers like conda and pixi from using wrapper commands in activatedRun without breaking the debugger, while remaining backwards-compatible since the two values are currently identical for all existing managers.
Configuration menu - View commit details
-
Copy full SHA for 9fc2797 - Browse repository at this point
Copy the full SHA 9fc2797View commit details -
feat: add tests and helper for using run.executable for interpreter n…
…ot activatedRun (microsoft#955)
Configuration menu - View commit details
-
Copy full SHA for 96a1935 - Browse repository at this point
Copy the full SHA 96a1935View commit details
Commits on Feb 17, 2026
-
Fix multiline environment variable parsing in .env files (microsoft#928)
* Initial plan * Fix multiline environment variable parsing in .env files Co-authored-by: rchiodo <19672699+rchiodo@users.noreply.github.com> * Improve escape sequence handling in environment parser Co-authored-by: rchiodo <19672699+rchiodo@users.noreply.github.com> * Update comment for regex 's' flag usage Co-authored-by: rchiodo <19672699+rchiodo@users.noreply.github.com> * Fix linter and prettier formatting issues Co-authored-by: rchiodo <19672699+rchiodo@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: rchiodo <19672699+rchiodo@users.noreply.github.com> Co-authored-by: Rich Chiodo <rchiodo@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 7253c44 - Browse repository at this point
Copy the full SHA 7253c44View commit details -
Fix PATH concatenation without separator in environment variable coll…
…ection (microsoft#958) * Initial plan * Fix PATH separator issue when appending to environment variable collection Co-authored-by: rchiodo <19672699+rchiodo@users.noreply.github.com> * Remove extra blank lines in test file Co-authored-by: rchiodo <19672699+rchiodo@users.noreply.github.com> * Fix prettier formatting in test file Co-authored-by: rchiodo <19672699+rchiodo@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: rchiodo <19672699+rchiodo@users.noreply.github.com> Co-authored-by: Rich Chiodo <rchiodo@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for db9362d - Browse repository at this point
Copy the full SHA db9362dView commit details
Commits on Feb 19, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 4c0fdc2 - Browse repository at this point
Copy the full SHA 4c0fdc2View commit details
Commits on Feb 23, 2026
-
no config debug: Fix error when multiple vscode windows are open (mic…
…rosoft#918) * no config debug: Fix error when multiple vscode windows are open Should fix microsoft#916, but getting this installed locally seemed sufficiently complicated that I gave up. Fix is: 1. Only watch a specific endpoint file 2. Make sure this endpoint file is unique (I imagine the workspace file path can be non unique across vscode windows) * [AI] Update tests * Fix typo * Remove driveby fix * Format * Cleanup test and try to fix it failing on windows I guess this is what I get for trusting AI at midnight. * Fix failing test on windows take 2 The error seems to be that `base` is `c:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\.noConfigDebugAdapterEndpoints` but `noConfigEndpointDir` is `C:\Users\RUNNER~1\AppData\Local\Temp\.noConfigDebugAdapterEndpoints` (the C is capitalised). Getting the fsPath of the URI should normalise the path the same as `base`. * Remove workspace from hash --------- Co-authored-by: Rich Chiodo <rchiodo@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 247c9bf - Browse repository at this point
Copy the full SHA 247c9bfView commit details
Commits on Feb 24, 2026
-
Add PR creation skill for Copilot (microsoft#962)
Add .github/instructions/pr.instructions.md to ensure PRs always include a bug or debt label. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for e0ec60c - Browse repository at this point
Copy the full SHA e0ec60cView commit details
Commits on Feb 25, 2026
-
Always quote Python executable path (microsoft#964)
* Always quote Python executable path On Windows, this would cause pahts like "C:\Program Files\" to fail launching the Python command as the blank space was not escaped properly. Add also a unit test to validate this change. Signed-off-by: Francesco Giancane <me@fgiancane8.dev> * stringUtils.ts: remove call to .replace() method for paths There is no need anymore to replace backslashes with forward slashes for paths on Windows, as the Python extension's `toCommandArgumentForPythonExt` function already handles this correctly. Signed-off-by: Francesco Giancane <me@fgiancane8.dev> * stringUtils.ts: restore replace call when normalizing string * remoteLaunchers: ensure test is normalizing paths Explicitly call `fileToCommandArgumentForPythonExt` when computing a path with spaces and check results are as expected. * stringUtils.ts: replace backslashes with forward-slashes only on non-Windows platforms. * Revert "remoteLaunchers: ensure test is normalizing paths" This reverts commit 32822e0. * remoteLaunchers.ts: feed platform-specific data to tests Use backward slashes on Windows and forward slashes on Unix-like OSes when testing correct behavior of path strings quotation. * Copy-paste error in comment. * remoteLaunchers.unit.test.ts: fix formatting issues --------- Signed-off-by: Francesco Giancane <me@fgiancane8.dev>
Configuration menu - View commit details
-
Copy full SHA for 33697c0 - Browse repository at this point
Copy the full SHA 33697c0View commit details
Commits on Mar 2, 2026
-
Bump webpack from 5.94.0 to 5.105.0 (microsoft#948)
Bumps [webpack](https://github.com/webpack/webpack) from 5.94.0 to 5.105.0. - [Release notes](https://github.com/webpack/webpack/releases) - [Changelog](https://github.com/webpack/webpack/blob/main/CHANGELOG.md) - [Commits](webpack/webpack@v5.94.0...v5.105.0) --- updated-dependencies: - dependency-name: webpack dependency-version: 5.105.0 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for fb20a64 - Browse repository at this point
Copy the full SHA fb20a64View commit details -
Bump qs from 6.14.1 to 6.14.2 (microsoft#956)
Bumps [qs](https://github.com/ljharb/qs) from 6.14.1 to 6.14.2. - [Changelog](https://github.com/ljharb/qs/blob/main/CHANGELOG.md) - [Commits](ljharb/qs@v6.14.1...v6.14.2) --- updated-dependencies: - dependency-name: qs dependency-version: 6.14.2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for e87b3cb - Browse repository at this point
Copy the full SHA e87b3cbView commit details -
Bump minimatch from 3.1.2 to 3.1.5 (microsoft#971)
Bumps [minimatch](https://github.com/isaacs/minimatch) from 3.1.2 to 3.1.5. - [Changelog](https://github.com/isaacs/minimatch/blob/main/changelog.md) - [Commits](isaacs/minimatch@v3.1.2...v3.1.5) --- updated-dependencies: - dependency-name: minimatch dependency-version: 3.1.5 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 1276ce9 - Browse repository at this point
Copy the full SHA 1276ce9View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff main...main