You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4b006f3
Browse filesBrowse the repository at this point in the historyBrowse files
Use public registries in GitHub Actions and authenticated release feeds (#1144)
* Use template-authenticated internal feeds for release builds
Match flake8/environments: pass Pylance_PublicPackages as the custom npm registry, use npm ci instead of the proxy-forcing ci:msft helper, and let PipAuthenticate supply Python feed credentials without per-step proxy overrides.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Honor authenticated release registries in ci:msft
Preserve the release variable names and ci:msft command. Honor the effective npm registry for lockfile rewriting and installation while inheriting the template-authenticated npmrc. Resolve PIP_PROXY_INDEX_URL from PipAuthenticate output so per-step pip settings retain feed credentials.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Use internal Microsoft package feed defaults
Replace packagefeedproxy defaults with Pylance_PublicPackages for npm and DevDiv/debugpy for pip. Preserve public defaults and update existing setup/registry tests. No workflow or credential changes.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Normalize registry overrides before rewriting and installing
Ensure slashless npm registry overrides end in a slash before building lockfile download URLs and invoking npm ci. Add regressions for public/internal registry rewrites and both uppercase/lowercase environment overrides while preserving npm authentication.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Use internal package feeds in GitHub workflows
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Authenticate GitHub package feed installs using Azure OIDC
Port the isort feed authentication action and npm/pip configuration. Retain per-platform debugger bundles because debugpy wheels are host-specific.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Use public registries in GitHub Actions
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copy file name to clipboardExpand all lines: README.md
+7-13Lines changed: 7 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ The Debugpy Extension for Visual Studio Code collects usage data and sends it to
57
57
58
58
### Local package feeds
59
59
60
-
Use Node.js supported by this repository and Python 3.10 or later. Both setup commands create or reuse `.venv` and install the Python bundling tools. Choose the appropriate setup below before installing dependencies. Committed lockfiles use public npm URLs; Microsoft setup rewrites working copies for proxy installs.
60
+
Use Node.js supported by this repository and Python 3.10 or later. Both setup commands create or reuse `.venv` and install the Python bundling tools. Choose the appropriate setup below before installing dependencies. Committed lockfiles use public npm URLs; Microsoft setup rewrites working copies for Microsoft feed installs.
61
61
62
62
#### Public contributors (non-Microsoft employees)
63
63
@@ -75,13 +75,13 @@ For subsequent npm installs, use `npm ci`. Public contributors do not need the M
75
75
76
76
> **Microsoft users only:** The commands in this section configure Microsoft package feeds. Public contributors should use the public setup above.
77
77
78
-
Use the Microsoft setup, which selects `https://packagefeedproxy.microsoft.io/npm/`and `https://packagefeedproxy.microsoft.io/pypi/simple/`for its child processes:
78
+
Use the Microsoft setup, which selects the `Pylance_PublicPackages` npm and PyPI feeds in `build/package-feeds.json`. Configure credentials for both feeds before running it; setup does not authenticate:
79
79
80
80
```bash
81
81
npm run setup:msft
82
82
```
83
83
84
-
Microsoft setup rewrites public npm and Yarn `resolved` URLs in the root `package-lock.json` to the npm proxy before running `npm ci`. Versions, integrity hashes, formatting, and private-feed URLs are preserved. The public setup leaves lockfiles unchanged.
84
+
Microsoft setup rewrites public npm and Yarn `resolved` URLs in the root `package-lock.json` to the Microsoft npm feed before running `npm ci`. Versions, integrity hashes, formatting, and private-feed URLs are preserved. The public setup leaves lockfiles unchanged.
85
85
86
86
After pulling a new lockfile from GitHub, rerun `npm run setup:msft`, or run the dependency-free rewrite step alone before your next install/build:
87
87
@@ -97,7 +97,7 @@ For subsequent root npm installs, use:
97
97
npm run ci:msft
98
98
```
99
99
100
-
This rewrites the root lockfile, then runs root `npm ci` with the proxy registry explicitly selected for package, audit, and metadata requests. Use `npm run setup:msft` for full setup, including Python dependencies.
100
+
This rewrites the root lockfile, then runs root `npm ci` with the Microsoft registry explicitly selected for package, audit, and metadata requests. Use `npm run setup:msft` for full setup, including Python dependencies.
101
101
102
102
Local setup, lockfile rewriting, and `ci:msft` share the feed URLs in `build/package-feeds.json`.
103
103
@@ -121,25 +121,19 @@ To normalize manually, run `npm run normalize-lockfile`, review the changes, and
121
121
122
122
### GitHub Actions package feeds
123
123
124
-
The PR and push workflows set `PIP_INDEX_URL` to `https://packagefeedproxy.microsoft.io/pypi/simple/` for pip and nox installs. Their Node installation steps select `https://packagefeedproxy.microsoft.io/npm/` explicitly through `npm run ci:msft`, so these workflows do not set `NPM_CONFIG_REGISTRY`. CodeQL retains both environment variables because its autobuild step does not use the install helper. The npm endpoint follows the [TypeScript CI package-feed-proxy job](https://github.com/microsoft/TypeScript/blob/main/.github/workflows/ci.yml).
125
-
126
-
The shared lint and VSIX build actions and applicable PR/push test jobs use `npm run ci:msft`, rewriting working-copy lockfile URLs before installation and explicitly selecting the proxy for npm requests. Workflows do not commit these rewrites or change local registry configuration or Dependabot configuration. Existing dependency caches are retained; the VSIX build also retains its offline-cache preference. CodeQL retains workflow-level feed settings for its autobuild step.
124
+
GitHub Actions use public npm and PyPI without feed authentication, including for fork PRs. Localization explicitly selects public npm because the shared action defaults to a proxy.
127
125
128
126
### Azure release package feeds
129
127
130
-
The DevDiv Azure stable/prerelease pipelines pass the npm proxy to their build/publish templates using `customNPMRegistry`. Their dependency install steps use `npm run ci:msft` to rewrite the root npm lockfile and install through the proxy.
131
-
132
-
Each Python bootstrap and bundled-library install step explicitly sets `PIP_INDEX_URL` from `PIP_PROXY_INDEX_URL`, selecting the pip proxy even when a template's authentication setup changes the job-level index. Release triggers, approval gates, signing, and publishing behavior are unchanged.
133
-
134
-
Dependabot continues to use public registries and its existing update settings. Legacy Azure stable, prerelease, and validation definitions are unchanged.
128
+
The DevDiv stable and prerelease pipelines pass the `Pylance_PublicPackages` npm feed to the shared template, which authenticates npm and the `DevDiv/debugpy` Python feed before build steps. Release triggers, approval gates, signing, and publishing are unchanged.
135
129
136
130
### Localization
137
131
138
132
The **Localization** GitHub workflow submits English strings using the [shared composite action and Python tooling](https://github.com/microsoft/vscode-python-ci/tree/main/actions/localization). Stable and pre-release DevDiv pipelines independently retrieve translations through Pylance-Eng's `pullLocalization: true`; releases never submit English or create translation-update PRs.
139
133
140
134
Both paths use `microsoft/vscode-python-extensions-loc`, branch **`dev`**, with canonical extension ID **`ms-python.debugpy`**. English XLF is stored in `src/en/ms-python.debugpy` and handbacks in `out/ms-python.debugpy`. The action and Azure tooling checkout are pinned to the same reviewed revision.
141
135
142
-
Configure the `PYTHON_LOCALIZATION_APP_ID` Actions variable and `PYTHON_LOCALIZATION_PRIVATE_KEY` secret here, or grant access to organization-level credentials. The app needs Contents write access only to the localization drop; the caller's repository token stays read-only. The shared action uses the Microsoft npm proxy and pinned localization CLI. Authorize the literal `Github-Pylance` service connection for the [pipeline templates](https://github.com/microsoft/pylance-eng), translation, and shared-tooling repository resources in both release pipelines.
136
+
Configure the `PYTHON_LOCALIZATION_APP_ID` Actions variable and `PYTHON_LOCALIZATION_PRIVATE_KEY` secret here, or grant access to organization-level credentials. The app needs Contents write access only to the localization drop; the caller's repository token stays read-only. The shared action uses public npm and a pinned localization CLI. Authorize the literal `Github-Pylance` service connection for the [pipeline templates](https://github.com/microsoft/pylance-eng), translation, and shared-tooling repository resources in both release pipelines.
143
137
144
138
Keep English `package.nls.json` tracked. Root `package.nls.<locale>.json` and `l10n/` runtime files are generated, git-ignored release outputs. VSCE must include generated locale files despite Git ignores. Local builds are English-only unless translations are imported explicitly (debugger pre-built assets remain available, but the release import runs after their overlay and is authoritative).
0 commit comments