Repository navigation
Use public registries in GitHub Actions and authenticated release feeds - #1144
Bill Schnurr (bschnurr) wants to merge 7 commits into
Conversation
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>
|
🔒 Automated review in progress — Rich Chiodo (@rchiodo) is auto-reviewing this PR. |
|
Reviewed commit: Result: 🔴 Verification detailsVerification: 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: C:\Program Files\RedHat\Podman\podman.EXE --connection pyrx-automation failed: stderr: Error: unable to start container "50175ab3578b53bce44a11c0b70be43ba626d5f476d48e38360eec24843dc54e": crun: open `memory.max` for writing: No such file or directory: OCI runtime attempted to invoke a command that was not found Test runs: none recorded. |
Rich Chiodo (rchiodo)
left a comment
There was a problem hiding this comment.
Approved via Review Center.
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>
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>
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>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
|
||
| env: | ||
| PIP_INDEX_URL: https://packagefeedproxy.microsoft.io/pypi/simple/ | ||
| PIP_INDEX_URL: https://pkgs.dev.azure.com/devdiv/DevDiv/_packaging/debugpy/pypi/simple/ |
There was a problem hiding this comment.
Issue · Please address or respond
📍 .github/workflows/pr-check.yml:9
High: The Skeptic reproduced HTTP 401 responses and failed pip resolution against this index, but this workflow and push-check.yml:14 provide no feed authentication before installing Python dependencies on fresh GitHub-hosted runners. Configure supported authentication before the first installation, and retain an accessible feed path for fork PRs where credentials cannot be supplied.
[verified]
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>
| sparse-checkout-cone-mode: false | ||
|
|
||
| - name: Authenticate package feeds | ||
| uses: ./ci-actions/.github/actions/authenticate-feeds |
There was a problem hiding this comment.
Issue · Please address or respond
📍 .github/workflows/pr-check.yml:85
[unverified] Prior High-priority feedback 4557182465 remains open: this pull_request workflow now authenticates unconditionally, but the requested nonprivileged feed path for fork PRs is still absent. Provide an accessible fork route across build, lint, and test jobs without granting untrusted PR code privileged feed credentials, and demonstrate trusted and fork dependency installation under the repository’s actual OIDC settings; current-HEAD authentication failure has not been reproduced.
[unverified]
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Do not auto-merge.
Summary
Pylance_PublicPackagesnpm feed viaAZURE_ARTIFACTS_FEEDand rely on the shared template's npm and PyPI authentication. They do not use packagefeedproxy.Verification