Use approved npm feed for Dependabot - #615
Eduardo Villalpando Mello (edvilme) wants to merge 4 commits into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: e6cc7d12-a7f4-48b7-a8ea-c4532ce17ea2
|
🔒 Automated review in progress — Bill Schnurr (@bschnurr) is auto-reviewing this PR. |
|
Result: Verification detailsVerification: The relevant tests could not be fully run in the isolated environment; this review is not fully verified. Summary: A Python smoke test successfully parsed the Dependabot YAML and verified the intended registry, OIDC identifiers, cooldown behavior, and `.npmrc` removal. The Prettier check timed out, and no repository tests cover the new Azure OIDC authentication path. An actual Dependabot update could not be exercised without the required managed identity and feed access. Confidence is therefore limited. Test runs: 2 passed, 2 not run
|
Bill Schnurr (bschnurr)
left a comment
There was a problem hiding this comment.
Approved via Review Center.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: e6cc7d12-a7f4-48b7-a8ea-c4532ce17ea2
|
Result: Verification detailsVerification: Isolated verification observed failures that were not classified as caused by this PR: Dependabot configuration semantic assertions. The relevant tests could not be fully run in the isolated environment; this review is not fully verified. Summary: The repository’s existing Prettier configuration check passed, including `.github/dependabot.yml`. Offline dependency installation also succeeded. No tests were added by the PR. Semantic assertions could not run because the unavailable `yaml` module blocked the ad-hoc check, and the actual Dependabot OIDC/feed authentication requires external infrastructure, leaving the core behavior unverified. Test runs: 1 passed, 1 failed, 1 not run
❌
|
|
Result: Verification detailsVerification: The relevant tests could not be fully run in the isolated environment; this review is not fully verified. Summary: Targeted checks passed: the Dependabot YAML is formatted and parses with the intended Azure OIDC registry, npm association, cooldowns, and `.npmrc` removal. Offline `npm ci` installed 643 packages successfully. The PR adds no tests. Live Dependabot authentication and feed access could not be exercised in the credential-free offline container, so verification is partial. Test runs: 4 passed
|
|
Result: Verification detailsVerification: Isolated verification observed failures that were not classified as caused by this PR: Dependabot configuration semantic assertions. Summary: The targeted Prettier check passed for `.github/dependabot.yml`, and offline dependency installation succeeded. No tests were added by the PR. A semantic assertion could not run because the repository lacks the attempted `yaml` module; this was unrelated to the PR. Dependabot's Azure OIDC authentication and feed access remain unverified. Test runs: 3 passed, 1 failed
❌
|
Summary - configure Dependabot npm updates to use the team-owned
Pylance_PublicPackagesAzure Artifacts feed - authenticate with Azure OIDC using the identity pattern established by microsoft/pyrx#9310 - retain the seven-day npm cooldown because@vscode/python-environmentsstill uses an explicit feed URL thatreplaces-basecannot redirect - retain the seven-day pip cooldown until an approved Python-feed path is confirmed - remove the project.npmrcthat forced Dependabot back to public npm ## Required infrastructure Do not removeno-mergeuntil the managed identity has feed access and a Dependabot federated credential for this repository. The credential must use issuerhttps://token.actions.msft.ghe.com, audienceapi://AzureADTokenExchange, and the exact repository subject emitted by Dependabot. The tenant and client IDs are identifiers, not secrets.