Fix Dependabot discovery of bundled Playwright; bump to 1.61.0 by Evangelink · Pull Request #9508 · microsoft/testfx

Amaury Levé (Evangelink) · 2026-06-29T17:49:26Z

Problem

Despite several attempts (#9365, #9422, #9452), Dependabot still never bumps the bundled Playwright version. As reported in #9362, it's stuck at 1.60.0 even though Microsoft.Playwright.MSTest.v4 1.61.0 has been published on nuget.org for days across multiple daily Dependabot runs.

Root cause

#9452 switched the Dependabot anchor for the bundled packages from a PackageReference (with ExcludeAssets="all") to a PackageDownload, on the theory that ExcludeAssets="all" hid the reference from Dependabot.

That theory is wrong on both counts:

Dependabot's NuGet ecosystem does not read PackageDownload items at all (dependabot/dependabot-core#2502). So after Fix Dependabot discovery of bundled Playwright via PackageDownload #9452 the Playwright anchor became invisible to Dependabot.
ExcludeAssets="all" does NOT hide a PackageReference from Dependabot — it only stops the package's assets from flowing into the build. Dependabot reads the PackageReference XML node, not the asset-flow rules. So the original #9422 anchor was the correct mechanism.

Aspire's bump in #9446 actually came from its ExcludeAssetsPackageReference (present during the #9422–#9452 window), not from its PackageDownload. Playwright simply had no newer release during that brief window (1.61 wasn't out yet); then #9452 removed the working anchor right before 1.61 shipped — and silently broke Aspire's discovery too (it only looks fine because it's already at latest).

Fix

MSTest.Acceptance.IntegrationTests.csproj — restore PackageReference ... ExcludeAssets="all" anchors (the kind Dependabot reads) for both Microsoft.Playwright.MSTest.v4 and Aspire.Hosting.Testing, while keeping the PackageDownload items for nupkg staging + *Version property correlation. Rewrote the comment to document the real Dependabot behavior. This dual-item layout is exactly what Aspire ran through green CI between Anchor SDK-bundled packages so Dependabot bumps them #9422 and Fix Dependabot discovery of bundled Playwright via PackageDownload #9452.
Directory.Packages.props — bump bundled Playwright 1.60.0 → 1.61.0 (both the MicrosoftPlaywrightVersion property and the literal Microsoft.Playwright.MSTest.v4PackageVersion, kept in sync so _ValidateBundledSdkFeatureVersions passes). Corrected the "condition 2" comment.

Verification

The change is config-only and structurally identical to the proven Aspire setup, so I'm confident in the MSBuild validity. The Dependabot behavior itself can only be confirmed on the next scheduled run against main.

#9452 switched the Dependabot anchor to PackageDownload, but Dependabot's NuGet ecosystem does not read PackageDownload items at all (dependabot/dependabot-core#2502), so the bundled Playwright version became invisible to Dependabot and stopped updating (1.61.0 was never proposed). Restore the PackageReference (ExcludeAssets="all") anchor for both Microsoft.Playwright.MSTest.v4 and Aspire.Hosting.Testing - ExcludeAssets only stops assets flowing into the build, it does not hide the reference from Dependabot. Keep the PackageDownload items for nupkg staging and property correlation. Bump bundled Playwright 1.60.0 -> 1.61.0. Fixes#9362 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot

Pull request overview

This PR adjusts how MSTest SDK–bundled packages are surfaced to Dependabot (so updates get proposed) and bumps the bundled Playwright version to 1.61.0.

Changes:

Restores PackageReference + ExcludeAssets="all" anchors (and keeps PackageDownload staging) for Playwright and Aspire in the MSTest acceptance integration test project.
Bumps MicrosoftPlaywrightVersion and the corresponding CPM PackageVersion for Microsoft.Playwright.MSTest.v4 from 1.60.0 to 1.61.0.
Updates in-file documentation to reflect Dependabot’s behavior and the intended anchor mechanism.

Show a summary per file

File	Description
test/IntegrationTests/MSTest.Acceptance.IntegrationTests/MSTest.Acceptance.IntegrationTests.csproj	Reintroduces Dependabot-visible `PackageReference` anchors while retaining `PackageDownload` entries used for nupkg staging.
Directory.Packages.props	Updates Playwright version to 1.61.0 and revises the “Dependabot discovery” guidance/comments for bundled SDK packages.

Review details

Files reviewed: 2/2 changed files
Comments generated: 1
Review effort level: Low

…isleading PackageDownload - Revert the manual 1.60.0 -> 1.61.0 bump: doing it here would leave the bundle at latest, so we couldn't tell whether the anchor fix actually let Dependabot propose the update. Leaving it at 1.60.0 means Dependabot's next run proposing 1.60.0 -> 1.61.0 is the proof the fix works. - Drop the Playwright PackageDownload anchor and its misleading comment (flagged in review): Dependabot ignores PackageDownload entirely, and nothing consumes Playwright's nupkg (only Aspire's is staged by CopyNuGetPackagesForTestAssets). The PackageReference (ExcludeAssets="all") is the sole Dependabot anchor; Aspire keeps its PackageDownload purely for nupkg staging. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Amaury Levé (Evangelink) · 2026-06-29T18:02:59Z

🧪 Test quality grade — PR #9508

No new or modified test methods were identified in the changed regions
of this PR. Nothing to grade.

_{Re-run with /grade-tests.}

🤖 Automated content by GitHub Copilot. Posted via a maintainer's GitHub token, so it appears under their account — the account owner did not write or approve this content personally. Generated by the Grade Tests on PR (on open / sync) workflow. · 123.4 AIC · ⌖ 12.5 AIC · ⊞ 43.8K · [◷]( · ◷)

Petr Pokorny (0101) · 2026-06-30T08:16:33Z

Heads-up: this diff doesn't appear to include the version bump described in the Fix section.

The description says it bumps bundled Playwright 1.60.0 → 1.61.0 in Directory.Packages.props (both the MicrosoftPlaywrightVersion property and the Microsoft.Playwright.MSTest.v4PackageVersion), but at the current head both still read 1.60.0:

Directory.Packages.props (~line 40): <MicrosoftPlaywrightVersion>1.60.0</MicrosoftPlaywrightVersion>
Directory.Packages.props (~line 177): <PackageVersion Include="Microsoft.Playwright.MSTest.v4" Version="1.60.0" />

The Directory.Packages.props hunks in the diff are limited to the comment block, and the PackageReference anchor restoration in MSTest.Acceptance.IntegrationTests.csproj looks correct. It just looks like the manual 1.61.0 edit didn't make it into the commits.

Could you double-check and push the version bump (so _ValidateBundledSdkFeatureVersions reflects it now rather than waiting on the next Dependabot run)? Alternatively, if this PR is meant to be the discovery-mechanism fix only, the title/description could be updated to match. Thanks!

Amaury Levé (Evangelink) · 2026-06-29T17:49:26Z

Fixes#9362

Problem

Despite several attempts (#9365, #9422, #9452), Dependabot still never bumps the bundled Playwright version. As reported in #9362, it's stuck at 1.60.0 even though Microsoft.Playwright.MSTest.v4 1.61.0 has been published on nuget.org for days across multiple daily Dependabot runs.

Root cause

#9452 switched the Dependabot anchor for the bundled packages from a PackageReference (with ExcludeAssets="all") to a PackageDownload, on the theory that ExcludeAssets="all" hid the reference from Dependabot.

That theory is wrong on both counts:

Dependabot's NuGet ecosystem does not read PackageDownload items at all (dependabot/dependabot-core#2502). So after Fix Dependabot discovery of bundled Playwright via PackageDownload #9452 the Playwright anchor became invisible to Dependabot.
ExcludeAssets="all" does NOT hide a PackageReference from Dependabot — it only stops the package's assets from flowing into the build. Dependabot reads the PackageReference XML node, not the asset-flow rules. So the original #9422 anchor was the correct mechanism.

Aspire's bump in #9446 actually came from its ExcludeAssetsPackageReference (present during the #9422–#9452 window), not from its PackageDownload. Playwright simply had no newer release during that brief window (1.61 wasn't out yet); then #9452 removed the working anchor right before 1.61 shipped — and silently broke Aspire's discovery too (it only looks fine because it's already at latest).

Fix

MSTest.Acceptance.IntegrationTests.csproj — restore PackageReference ... ExcludeAssets="all" anchors (the kind Dependabot reads) for both Microsoft.Playwright.MSTest.v4 and Aspire.Hosting.Testing, while keeping the PackageDownload items for nupkg staging + *Version property correlation. Rewrote the comment to document the real Dependabot behavior. This dual-item layout is exactly what Aspire ran through green CI between Anchor SDK-bundled packages so Dependabot bumps them #9422 and Fix Dependabot discovery of bundled Playwright via PackageDownload #9452.
Directory.Packages.props — bump bundled Playwright 1.60.0 → 1.61.0 (both the MicrosoftPlaywrightVersion property and the literal Microsoft.Playwright.MSTest.v4PackageVersion, kept in sync so _ValidateBundledSdkFeatureVersions passes). Corrected the "condition 2" comment.

Verification

The change is config-only and structurally identical to the proven Aspire setup, so I'm confident in the MSBuild validity. The Dependabot behavior itself can only be confirmed on the next scheduled run against main.

#9452 switched the Dependabot anchor to PackageDownload, but Dependabot's NuGet ecosystem does not read PackageDownload items at all (dependabot/dependabot-core#2502), so the bundled Playwright version became invisible to Dependabot and stopped updating (1.61.0 was never proposed). Restore the PackageReference (ExcludeAssets="all") anchor for both Microsoft.Playwright.MSTest.v4 and Aspire.Hosting.Testing - ExcludeAssets only stops assets flowing into the build, it does not hide the reference from Dependabot. Keep the PackageDownload items for nupkg staging and property correlation. Bump bundled Playwright 1.60.0 -> 1.61.0. Fixes#9362 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot

Pull request overview

This PR adjusts how MSTest SDK–bundled packages are surfaced to Dependabot (so updates get proposed) and bumps the bundled Playwright version to 1.61.0.

Changes:

Restores PackageReference + ExcludeAssets="all" anchors (and keeps PackageDownload staging) for Playwright and Aspire in the MSTest acceptance integration test project.
Bumps MicrosoftPlaywrightVersion and the corresponding CPM PackageVersion for Microsoft.Playwright.MSTest.v4 from 1.60.0 to 1.61.0.
Updates in-file documentation to reflect Dependabot’s behavior and the intended anchor mechanism.

Show a summary per file

File	Description
test/IntegrationTests/MSTest.Acceptance.IntegrationTests/MSTest.Acceptance.IntegrationTests.csproj	Reintroduces Dependabot-visible `PackageReference` anchors while retaining `PackageDownload` entries used for nupkg staging.
Directory.Packages.props	Updates Playwright version to 1.61.0 and revises the “Dependabot discovery” guidance/comments for bundled SDK packages.

Review details

Files reviewed: 2/2 changed files
Comments generated: 1
Review effort level: Low

…isleading PackageDownload - Revert the manual 1.60.0 -> 1.61.0 bump: doing it here would leave the bundle at latest, so we couldn't tell whether the anchor fix actually let Dependabot propose the update. Leaving it at 1.60.0 means Dependabot's next run proposing 1.60.0 -> 1.61.0 is the proof the fix works. - Drop the Playwright PackageDownload anchor and its misleading comment (flagged in review): Dependabot ignores PackageDownload entirely, and nothing consumes Playwright's nupkg (only Aspire's is staged by CopyNuGetPackagesForTestAssets). The PackageReference (ExcludeAssets="all") is the sole Dependabot anchor; Aspire keeps its PackageDownload purely for nupkg staging. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Amaury Levé (Evangelink) · 2026-06-29T18:02:59Z

🧪 Test quality grade — PR #9508

No new or modified test methods were identified in the changed regions
of this PR. Nothing to grade.

_{Re-run with /grade-tests.}

🤖 Automated content by GitHub Copilot. Posted via a maintainer's GitHub token, so it appears under their account — the account owner did not write or approve this content personally. Generated by the Grade Tests on PR (on open / sync) workflow. · 123.4 AIC · ⌖ 12.5 AIC · ⊞ 43.8K · [◷]( · ◷)

Petr Pokorny (0101) · 2026-06-30T08:16:33Z

Heads-up: this diff doesn't appear to include the version bump described in the Fix section.

The description says it bumps bundled Playwright 1.60.0 → 1.61.0 in Directory.Packages.props (both the MicrosoftPlaywrightVersion property and the Microsoft.Playwright.MSTest.v4PackageVersion), but at the current head both still read 1.60.0:

Directory.Packages.props (~line 40): <MicrosoftPlaywrightVersion>1.60.0</MicrosoftPlaywrightVersion>
Directory.Packages.props (~line 177): <PackageVersion Include="Microsoft.Playwright.MSTest.v4" Version="1.60.0" />

The Directory.Packages.props hunks in the diff are limited to the comment block, and the PackageReference anchor restoration in MSTest.Acceptance.IntegrationTests.csproj looks correct. It just looks like the manual 1.61.0 edit didn't make it into the commits.

Could you double-check and push the version bump (so _ValidateBundledSdkFeatureVersions reflects it now rather than waiting on the next Dependabot run)? Alternatively, if this PR is meant to be the discovery-mechanism fix only, the title/description could be updated to match. Thanks!

Amaury Levé (Evangelink) · 2026-06-29T17:49:26Z

Fixes#9362

Problem

Despite several attempts (#9365, #9422, #9452), Dependabot still never bumps the bundled Playwright version. As reported in #9362, it's stuck at 1.60.0 even though Microsoft.Playwright.MSTest.v4 1.61.0 has been published on nuget.org for days across multiple daily Dependabot runs.

Root cause

#9452 switched the Dependabot anchor for the bundled packages from a PackageReference (with ExcludeAssets="all") to a PackageDownload, on the theory that ExcludeAssets="all" hid the reference from Dependabot.

That theory is wrong on both counts:

Dependabot's NuGet ecosystem does not read PackageDownload items at all (dependabot/dependabot-core#2502). So after Fix Dependabot discovery of bundled Playwright via PackageDownload #9452 the Playwright anchor became invisible to Dependabot.
ExcludeAssets="all" does NOT hide a PackageReference from Dependabot — it only stops the package's assets from flowing into the build. Dependabot reads the PackageReference XML node, not the asset-flow rules. So the original #9422 anchor was the correct mechanism.

Aspire's bump in #9446 actually came from its ExcludeAssetsPackageReference (present during the #9422–#9452 window), not from its PackageDownload. Playwright simply had no newer release during that brief window (1.61 wasn't out yet); then #9452 removed the working anchor right before 1.61 shipped — and silently broke Aspire's discovery too (it only looks fine because it's already at latest).

Fix

MSTest.Acceptance.IntegrationTests.csproj — restore PackageReference ... ExcludeAssets="all" anchors (the kind Dependabot reads) for both Microsoft.Playwright.MSTest.v4 and Aspire.Hosting.Testing, while keeping the PackageDownload items for nupkg staging + *Version property correlation. Rewrote the comment to document the real Dependabot behavior. This dual-item layout is exactly what Aspire ran through green CI between Anchor SDK-bundled packages so Dependabot bumps them #9422 and Fix Dependabot discovery of bundled Playwright via PackageDownload #9452.
Directory.Packages.props — bump bundled Playwright 1.60.0 → 1.61.0 (both the MicrosoftPlaywrightVersion property and the literal Microsoft.Playwright.MSTest.v4PackageVersion, kept in sync so _ValidateBundledSdkFeatureVersions passes). Corrected the "condition 2" comment.

Verification

The change is config-only and structurally identical to the proven Aspire setup, so I'm confident in the MSBuild validity. The Dependabot behavior itself can only be confirmed on the next scheduled run against main.

#9452 switched the Dependabot anchor to PackageDownload, but Dependabot's NuGet ecosystem does not read PackageDownload items at all (dependabot/dependabot-core#2502), so the bundled Playwright version became invisible to Dependabot and stopped updating (1.61.0 was never proposed). Restore the PackageReference (ExcludeAssets="all") anchor for both Microsoft.Playwright.MSTest.v4 and Aspire.Hosting.Testing - ExcludeAssets only stops assets flowing into the build, it does not hide the reference from Dependabot. Keep the PackageDownload items for nupkg staging and property correlation. Bump bundled Playwright 1.60.0 -> 1.61.0. Fixes#9362 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot

Pull request overview

This PR adjusts how MSTest SDK–bundled packages are surfaced to Dependabot (so updates get proposed) and bumps the bundled Playwright version to 1.61.0.

Changes:

Restores PackageReference + ExcludeAssets="all" anchors (and keeps PackageDownload staging) for Playwright and Aspire in the MSTest acceptance integration test project.
Bumps MicrosoftPlaywrightVersion and the corresponding CPM PackageVersion for Microsoft.Playwright.MSTest.v4 from 1.60.0 to 1.61.0.
Updates in-file documentation to reflect Dependabot’s behavior and the intended anchor mechanism.

Show a summary per file

File	Description
test/IntegrationTests/MSTest.Acceptance.IntegrationTests/MSTest.Acceptance.IntegrationTests.csproj	Reintroduces Dependabot-visible `PackageReference` anchors while retaining `PackageDownload` entries used for nupkg staging.
Directory.Packages.props	Updates Playwright version to 1.61.0 and revises the “Dependabot discovery” guidance/comments for bundled SDK packages.

Review details

Files reviewed: 2/2 changed files
Comments generated: 1
Review effort level: Low

…isleading PackageDownload - Revert the manual 1.60.0 -> 1.61.0 bump: doing it here would leave the bundle at latest, so we couldn't tell whether the anchor fix actually let Dependabot propose the update. Leaving it at 1.60.0 means Dependabot's next run proposing 1.60.0 -> 1.61.0 is the proof the fix works. - Drop the Playwright PackageDownload anchor and its misleading comment (flagged in review): Dependabot ignores PackageDownload entirely, and nothing consumes Playwright's nupkg (only Aspire's is staged by CopyNuGetPackagesForTestAssets). The PackageReference (ExcludeAssets="all") is the sole Dependabot anchor; Aspire keeps its PackageDownload purely for nupkg staging. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Amaury Levé (Evangelink) · 2026-06-29T18:02:59Z

🧪 Test quality grade — PR #9508

No new or modified test methods were identified in the changed regions
of this PR. Nothing to grade.

_{Re-run with /grade-tests.}

🤖 Automated content by GitHub Copilot. Posted via a maintainer's GitHub token, so it appears under their account — the account owner did not write or approve this content personally. Generated by the Grade Tests on PR (on open / sync) workflow. · 123.4 AIC · ⌖ 12.5 AIC · ⊞ 43.8K · [◷]( · ◷)

Petr Pokorny (0101) · 2026-06-30T08:16:33Z

Heads-up: this diff doesn't appear to include the version bump described in the Fix section.

The description says it bumps bundled Playwright 1.60.0 → 1.61.0 in Directory.Packages.props (both the MicrosoftPlaywrightVersion property and the Microsoft.Playwright.MSTest.v4PackageVersion), but at the current head both still read 1.60.0:

Directory.Packages.props (~line 40): <MicrosoftPlaywrightVersion>1.60.0</MicrosoftPlaywrightVersion>
Directory.Packages.props (~line 177): <PackageVersion Include="Microsoft.Playwright.MSTest.v4" Version="1.60.0" />

The Directory.Packages.props hunks in the diff are limited to the comment block, and the PackageReference anchor restoration in MSTest.Acceptance.IntegrationTests.csproj looks correct. It just looks like the manual 1.61.0 edit didn't make it into the commits.

Could you double-check and push the version bump (so _ValidateBundledSdkFeatureVersions reflects it now rather than waiting on the next Dependabot run)? Alternatively, if this PR is meant to be the discovery-mechanism fix only, the title/description could be updated to match. Thanks!

Amaury Levé (Evangelink) · 2026-06-29T17:49:26Z

Fixes#9362

Problem

Despite several attempts (#9365, #9422, #9452), Dependabot still never bumps the bundled Playwright version. As reported in #9362, it's stuck at 1.60.0 even though Microsoft.Playwright.MSTest.v4 1.61.0 has been published on nuget.org for days across multiple daily Dependabot runs.

Root cause

#9452 switched the Dependabot anchor for the bundled packages from a PackageReference (with ExcludeAssets="all") to a PackageDownload, on the theory that ExcludeAssets="all" hid the reference from Dependabot.

That theory is wrong on both counts:

Dependabot's NuGet ecosystem does not read PackageDownload items at all (dependabot/dependabot-core#2502). So after Fix Dependabot discovery of bundled Playwright via PackageDownload #9452 the Playwright anchor became invisible to Dependabot.
ExcludeAssets="all" does NOT hide a PackageReference from Dependabot — it only stops the package's assets from flowing into the build. Dependabot reads the PackageReference XML node, not the asset-flow rules. So the original #9422 anchor was the correct mechanism.

Aspire's bump in #9446 actually came from its ExcludeAssetsPackageReference (present during the #9422–#9452 window), not from its PackageDownload. Playwright simply had no newer release during that brief window (1.61 wasn't out yet); then #9452 removed the working anchor right before 1.61 shipped — and silently broke Aspire's discovery too (it only looks fine because it's already at latest).

Fix

MSTest.Acceptance.IntegrationTests.csproj — restore PackageReference ... ExcludeAssets="all" anchors (the kind Dependabot reads) for both Microsoft.Playwright.MSTest.v4 and Aspire.Hosting.Testing, while keeping the PackageDownload items for nupkg staging + *Version property correlation. Rewrote the comment to document the real Dependabot behavior. This dual-item layout is exactly what Aspire ran through green CI between Anchor SDK-bundled packages so Dependabot bumps them #9422 and Fix Dependabot discovery of bundled Playwright via PackageDownload #9452.
Directory.Packages.props — bump bundled Playwright 1.60.0 → 1.61.0 (both the MicrosoftPlaywrightVersion property and the literal Microsoft.Playwright.MSTest.v4PackageVersion, kept in sync so _ValidateBundledSdkFeatureVersions passes). Corrected the "condition 2" comment.

Verification

The change is config-only and structurally identical to the proven Aspire setup, so I'm confident in the MSBuild validity. The Dependabot behavior itself can only be confirmed on the next scheduled run against main.

#9452 switched the Dependabot anchor to PackageDownload, but Dependabot's NuGet ecosystem does not read PackageDownload items at all (dependabot/dependabot-core#2502), so the bundled Playwright version became invisible to Dependabot and stopped updating (1.61.0 was never proposed). Restore the PackageReference (ExcludeAssets="all") anchor for both Microsoft.Playwright.MSTest.v4 and Aspire.Hosting.Testing - ExcludeAssets only stops assets flowing into the build, it does not hide the reference from Dependabot. Keep the PackageDownload items for nupkg staging and property correlation. Bump bundled Playwright 1.60.0 -> 1.61.0. Fixes#9362 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot

Pull request overview

This PR adjusts how MSTest SDK–bundled packages are surfaced to Dependabot (so updates get proposed) and bumps the bundled Playwright version to 1.61.0.

Changes:

Restores PackageReference + ExcludeAssets="all" anchors (and keeps PackageDownload staging) for Playwright and Aspire in the MSTest acceptance integration test project.
Bumps MicrosoftPlaywrightVersion and the corresponding CPM PackageVersion for Microsoft.Playwright.MSTest.v4 from 1.60.0 to 1.61.0.
Updates in-file documentation to reflect Dependabot’s behavior and the intended anchor mechanism.

Show a summary per file

File	Description
test/IntegrationTests/MSTest.Acceptance.IntegrationTests/MSTest.Acceptance.IntegrationTests.csproj	Reintroduces Dependabot-visible `PackageReference` anchors while retaining `PackageDownload` entries used for nupkg staging.
Directory.Packages.props	Updates Playwright version to 1.61.0 and revises the “Dependabot discovery” guidance/comments for bundled SDK packages.

Review details

Files reviewed: 2/2 changed files
Comments generated: 1
Review effort level: Low

…isleading PackageDownload - Revert the manual 1.60.0 -> 1.61.0 bump: doing it here would leave the bundle at latest, so we couldn't tell whether the anchor fix actually let Dependabot propose the update. Leaving it at 1.60.0 means Dependabot's next run proposing 1.60.0 -> 1.61.0 is the proof the fix works. - Drop the Playwright PackageDownload anchor and its misleading comment (flagged in review): Dependabot ignores PackageDownload entirely, and nothing consumes Playwright's nupkg (only Aspire's is staged by CopyNuGetPackagesForTestAssets). The PackageReference (ExcludeAssets="all") is the sole Dependabot anchor; Aspire keeps its PackageDownload purely for nupkg staging. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Amaury Levé (Evangelink) · 2026-06-29T18:02:59Z

🧪 Test quality grade — PR #9508

No new or modified test methods were identified in the changed regions
of this PR. Nothing to grade.

_{Re-run with /grade-tests.}

🤖 Automated content by GitHub Copilot. Posted via a maintainer's GitHub token, so it appears under their account — the account owner did not write or approve this content personally. Generated by the Grade Tests on PR (on open / sync) workflow. · 123.4 AIC · ⌖ 12.5 AIC · ⊞ 43.8K · [◷]( · ◷)

Petr Pokorny (0101) · 2026-06-30T08:16:33Z

Heads-up: this diff doesn't appear to include the version bump described in the Fix section.

The description says it bumps bundled Playwright 1.60.0 → 1.61.0 in Directory.Packages.props (both the MicrosoftPlaywrightVersion property and the Microsoft.Playwright.MSTest.v4PackageVersion), but at the current head both still read 1.60.0:

Directory.Packages.props (~line 40): <MicrosoftPlaywrightVersion>1.60.0</MicrosoftPlaywrightVersion>
Directory.Packages.props (~line 177): <PackageVersion Include="Microsoft.Playwright.MSTest.v4" Version="1.60.0" />

The Directory.Packages.props hunks in the diff are limited to the comment block, and the PackageReference anchor restoration in MSTest.Acceptance.IntegrationTests.csproj looks correct. It just looks like the manual 1.61.0 edit didn't make it into the commits.

Could you double-check and push the version bump (so _ValidateBundledSdkFeatureVersions reflects it now rather than waiting on the next Dependabot run)? Alternatively, if this PR is meant to be the discovery-mechanism fix only, the title/description could be updated to match. Thanks!

Amaury Levé (Evangelink) · 2026-06-29T17:49:26Z

Fixes#9362

Problem

Despite several attempts (#9365, #9422, #9452), Dependabot still never bumps the bundled Playwright version. As reported in #9362, it's stuck at 1.60.0 even though Microsoft.Playwright.MSTest.v4 1.61.0 has been published on nuget.org for days across multiple daily Dependabot runs.

Root cause

#9452 switched the Dependabot anchor for the bundled packages from a PackageReference (with ExcludeAssets="all") to a PackageDownload, on the theory that ExcludeAssets="all" hid the reference from Dependabot.

That theory is wrong on both counts:

Dependabot's NuGet ecosystem does not read PackageDownload items at all (dependabot/dependabot-core#2502). So after Fix Dependabot discovery of bundled Playwright via PackageDownload #9452 the Playwright anchor became invisible to Dependabot.
ExcludeAssets="all" does NOT hide a PackageReference from Dependabot — it only stops the package's assets from flowing into the build. Dependabot reads the PackageReference XML node, not the asset-flow rules. So the original #9422 anchor was the correct mechanism.

Aspire's bump in #9446 actually came from its ExcludeAssetsPackageReference (present during the #9422–#9452 window), not from its PackageDownload. Playwright simply had no newer release during that brief window (1.61 wasn't out yet); then #9452 removed the working anchor right before 1.61 shipped — and silently broke Aspire's discovery too (it only looks fine because it's already at latest).

Fix

MSTest.Acceptance.IntegrationTests.csproj — restore PackageReference ... ExcludeAssets="all" anchors (the kind Dependabot reads) for both Microsoft.Playwright.MSTest.v4 and Aspire.Hosting.Testing, while keeping the PackageDownload items for nupkg staging + *Version property correlation. Rewrote the comment to document the real Dependabot behavior. This dual-item layout is exactly what Aspire ran through green CI between Anchor SDK-bundled packages so Dependabot bumps them #9422 and Fix Dependabot discovery of bundled Playwright via PackageDownload #9452.
Directory.Packages.props — bump bundled Playwright 1.60.0 → 1.61.0 (both the MicrosoftPlaywrightVersion property and the literal Microsoft.Playwright.MSTest.v4PackageVersion, kept in sync so _ValidateBundledSdkFeatureVersions passes). Corrected the "condition 2" comment.

Verification

The change is config-only and structurally identical to the proven Aspire setup, so I'm confident in the MSBuild validity. The Dependabot behavior itself can only be confirmed on the next scheduled run against main.

#9452 switched the Dependabot anchor to PackageDownload, but Dependabot's NuGet ecosystem does not read PackageDownload items at all (dependabot/dependabot-core#2502), so the bundled Playwright version became invisible to Dependabot and stopped updating (1.61.0 was never proposed). Restore the PackageReference (ExcludeAssets="all") anchor for both Microsoft.Playwright.MSTest.v4 and Aspire.Hosting.Testing - ExcludeAssets only stops assets flowing into the build, it does not hide the reference from Dependabot. Keep the PackageDownload items for nupkg staging and property correlation. Bump bundled Playwright 1.60.0 -> 1.61.0. Fixes#9362 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot

Pull request overview

This PR adjusts how MSTest SDK–bundled packages are surfaced to Dependabot (so updates get proposed) and bumps the bundled Playwright version to 1.61.0.

Changes:

Restores PackageReference + ExcludeAssets="all" anchors (and keeps PackageDownload staging) for Playwright and Aspire in the MSTest acceptance integration test project.
Bumps MicrosoftPlaywrightVersion and the corresponding CPM PackageVersion for Microsoft.Playwright.MSTest.v4 from 1.60.0 to 1.61.0.
Updates in-file documentation to reflect Dependabot’s behavior and the intended anchor mechanism.

Show a summary per file

File	Description
test/IntegrationTests/MSTest.Acceptance.IntegrationTests/MSTest.Acceptance.IntegrationTests.csproj	Reintroduces Dependabot-visible `PackageReference` anchors while retaining `PackageDownload` entries used for nupkg staging.
Directory.Packages.props	Updates Playwright version to 1.61.0 and revises the “Dependabot discovery” guidance/comments for bundled SDK packages.

Review details

Files reviewed: 2/2 changed files
Comments generated: 1
Review effort level: Low

…isleading PackageDownload - Revert the manual 1.60.0 -> 1.61.0 bump: doing it here would leave the bundle at latest, so we couldn't tell whether the anchor fix actually let Dependabot propose the update. Leaving it at 1.60.0 means Dependabot's next run proposing 1.60.0 -> 1.61.0 is the proof the fix works. - Drop the Playwright PackageDownload anchor and its misleading comment (flagged in review): Dependabot ignores PackageDownload entirely, and nothing consumes Playwright's nupkg (only Aspire's is staged by CopyNuGetPackagesForTestAssets). The PackageReference (ExcludeAssets="all") is the sole Dependabot anchor; Aspire keeps its PackageDownload purely for nupkg staging. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Amaury Levé (Evangelink) · 2026-06-29T18:02:59Z

🧪 Test quality grade — PR #9508

No new or modified test methods were identified in the changed regions
of this PR. Nothing to grade.

_{Re-run with /grade-tests.}

🤖 Automated content by GitHub Copilot. Posted via a maintainer's GitHub token, so it appears under their account — the account owner did not write or approve this content personally. Generated by the Grade Tests on PR (on open / sync) workflow. · 123.4 AIC · ⌖ 12.5 AIC · ⊞ 43.8K · [◷]( · ◷)

Petr Pokorny (0101) · 2026-06-30T08:16:33Z

Heads-up: this diff doesn't appear to include the version bump described in the Fix section.

The description says it bumps bundled Playwright 1.60.0 → 1.61.0 in Directory.Packages.props (both the MicrosoftPlaywrightVersion property and the Microsoft.Playwright.MSTest.v4PackageVersion), but at the current head both still read 1.60.0:

Directory.Packages.props (~line 40): <MicrosoftPlaywrightVersion>1.60.0</MicrosoftPlaywrightVersion>
Directory.Packages.props (~line 177): <PackageVersion Include="Microsoft.Playwright.MSTest.v4" Version="1.60.0" />

The Directory.Packages.props hunks in the diff are limited to the comment block, and the PackageReference anchor restoration in MSTest.Acceptance.IntegrationTests.csproj looks correct. It just looks like the manual 1.61.0 edit didn't make it into the commits.

Could you double-check and push the version bump (so _ValidateBundledSdkFeatureVersions reflects it now rather than waiting on the next Dependabot run)? Alternatively, if this PR is meant to be the discovery-mechanism fix only, the title/description could be updated to match. Thanks!

Amaury Levé (Evangelink) · 2026-06-29T17:49:26Z

Fixes#9362

Problem

Despite several attempts (#9365, #9422, #9452), Dependabot still never bumps the bundled Playwright version. As reported in #9362, it's stuck at 1.60.0 even though Microsoft.Playwright.MSTest.v4 1.61.0 has been published on nuget.org for days across multiple daily Dependabot runs.

Root cause

#9452 switched the Dependabot anchor for the bundled packages from a PackageReference (with ExcludeAssets="all") to a PackageDownload, on the theory that ExcludeAssets="all" hid the reference from Dependabot.

That theory is wrong on both counts:

Dependabot's NuGet ecosystem does not read PackageDownload items at all (dependabot/dependabot-core#2502). So after Fix Dependabot discovery of bundled Playwright via PackageDownload #9452 the Playwright anchor became invisible to Dependabot.
ExcludeAssets="all" does NOT hide a PackageReference from Dependabot — it only stops the package's assets from flowing into the build. Dependabot reads the PackageReference XML node, not the asset-flow rules. So the original #9422 anchor was the correct mechanism.

Aspire's bump in #9446 actually came from its ExcludeAssetsPackageReference (present during the #9422–#9452 window), not from its PackageDownload. Playwright simply had no newer release during that brief window (1.61 wasn't out yet); then #9452 removed the working anchor right before 1.61 shipped — and silently broke Aspire's discovery too (it only looks fine because it's already at latest).

Fix

MSTest.Acceptance.IntegrationTests.csproj — restore PackageReference ... ExcludeAssets="all" anchors (the kind Dependabot reads) for both Microsoft.Playwright.MSTest.v4 and Aspire.Hosting.Testing, while keeping the PackageDownload items for nupkg staging + *Version property correlation. Rewrote the comment to document the real Dependabot behavior. This dual-item layout is exactly what Aspire ran through green CI between Anchor SDK-bundled packages so Dependabot bumps them #9422 and Fix Dependabot discovery of bundled Playwright via PackageDownload #9452.
Directory.Packages.props — bump bundled Playwright 1.60.0 → 1.61.0 (both the MicrosoftPlaywrightVersion property and the literal Microsoft.Playwright.MSTest.v4PackageVersion, kept in sync so _ValidateBundledSdkFeatureVersions passes). Corrected the "condition 2" comment.

Verification

The change is config-only and structurally identical to the proven Aspire setup, so I'm confident in the MSBuild validity. The Dependabot behavior itself can only be confirmed on the next scheduled run against main.

#9452 switched the Dependabot anchor to PackageDownload, but Dependabot's NuGet ecosystem does not read PackageDownload items at all (dependabot/dependabot-core#2502), so the bundled Playwright version became invisible to Dependabot and stopped updating (1.61.0 was never proposed). Restore the PackageReference (ExcludeAssets="all") anchor for both Microsoft.Playwright.MSTest.v4 and Aspire.Hosting.Testing - ExcludeAssets only stops assets flowing into the build, it does not hide the reference from Dependabot. Keep the PackageDownload items for nupkg staging and property correlation. Bump bundled Playwright 1.60.0 -> 1.61.0. Fixes#9362 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot

Pull request overview

This PR adjusts how MSTest SDK–bundled packages are surfaced to Dependabot (so updates get proposed) and bumps the bundled Playwright version to 1.61.0.

Changes:

Restores PackageReference + ExcludeAssets="all" anchors (and keeps PackageDownload staging) for Playwright and Aspire in the MSTest acceptance integration test project.
Bumps MicrosoftPlaywrightVersion and the corresponding CPM PackageVersion for Microsoft.Playwright.MSTest.v4 from 1.60.0 to 1.61.0.
Updates in-file documentation to reflect Dependabot’s behavior and the intended anchor mechanism.

Show a summary per file

File	Description
test/IntegrationTests/MSTest.Acceptance.IntegrationTests/MSTest.Acceptance.IntegrationTests.csproj	Reintroduces Dependabot-visible `PackageReference` anchors while retaining `PackageDownload` entries used for nupkg staging.
Directory.Packages.props	Updates Playwright version to 1.61.0 and revises the “Dependabot discovery” guidance/comments for bundled SDK packages.

Review details

Files reviewed: 2/2 changed files
Comments generated: 1
Review effort level: Low

…isleading PackageDownload - Revert the manual 1.60.0 -> 1.61.0 bump: doing it here would leave the bundle at latest, so we couldn't tell whether the anchor fix actually let Dependabot propose the update. Leaving it at 1.60.0 means Dependabot's next run proposing 1.60.0 -> 1.61.0 is the proof the fix works. - Drop the Playwright PackageDownload anchor and its misleading comment (flagged in review): Dependabot ignores PackageDownload entirely, and nothing consumes Playwright's nupkg (only Aspire's is staged by CopyNuGetPackagesForTestAssets). The PackageReference (ExcludeAssets="all") is the sole Dependabot anchor; Aspire keeps its PackageDownload purely for nupkg staging. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Amaury Levé (Evangelink) · 2026-06-29T18:02:59Z

🧪 Test quality grade — PR #9508

No new or modified test methods were identified in the changed regions
of this PR. Nothing to grade.

_{Re-run with /grade-tests.}

🤖 Automated content by GitHub Copilot. Posted via a maintainer's GitHub token, so it appears under their account — the account owner did not write or approve this content personally. Generated by the Grade Tests on PR (on open / sync) workflow. · 123.4 AIC · ⌖ 12.5 AIC · ⊞ 43.8K · [◷]( · ◷)

Petr Pokorny (0101) · 2026-06-30T08:16:33Z

Heads-up: this diff doesn't appear to include the version bump described in the Fix section.

The description says it bumps bundled Playwright 1.60.0 → 1.61.0 in Directory.Packages.props (both the MicrosoftPlaywrightVersion property and the Microsoft.Playwright.MSTest.v4PackageVersion), but at the current head both still read 1.60.0:

Directory.Packages.props (~line 40): <MicrosoftPlaywrightVersion>1.60.0</MicrosoftPlaywrightVersion>
Directory.Packages.props (~line 177): <PackageVersion Include="Microsoft.Playwright.MSTest.v4" Version="1.60.0" />

The Directory.Packages.props hunks in the diff are limited to the comment block, and the PackageReference anchor restoration in MSTest.Acceptance.IntegrationTests.csproj looks correct. It just looks like the manual 1.61.0 edit didn't make it into the commits.

Could you double-check and push the version bump (so _ValidateBundledSdkFeatureVersions reflects it now rather than waiting on the next Dependabot run)? Alternatively, if this PR is meant to be the discovery-mechanism fix only, the title/description could be updated to match. Thanks!

Amaury Levé (Evangelink) · 2026-06-29T17:49:26Z

Fixes#9362

Problem

Despite several attempts (#9365, #9422, #9452), Dependabot still never bumps the bundled Playwright version. As reported in #9362, it's stuck at 1.60.0 even though Microsoft.Playwright.MSTest.v4 1.61.0 has been published on nuget.org for days across multiple daily Dependabot runs.

Root cause

#9452 switched the Dependabot anchor for the bundled packages from a PackageReference (with ExcludeAssets="all") to a PackageDownload, on the theory that ExcludeAssets="all" hid the reference from Dependabot.

That theory is wrong on both counts:

Dependabot's NuGet ecosystem does not read PackageDownload items at all (dependabot/dependabot-core#2502). So after Fix Dependabot discovery of bundled Playwright via PackageDownload #9452 the Playwright anchor became invisible to Dependabot.
ExcludeAssets="all" does NOT hide a PackageReference from Dependabot — it only stops the package's assets from flowing into the build. Dependabot reads the PackageReference XML node, not the asset-flow rules. So the original #9422 anchor was the correct mechanism.

Aspire's bump in #9446 actually came from its ExcludeAssetsPackageReference (present during the #9422–#9452 window), not from its PackageDownload. Playwright simply had no newer release during that brief window (1.61 wasn't out yet); then #9452 removed the working anchor right before 1.61 shipped — and silently broke Aspire's discovery too (it only looks fine because it's already at latest).

Fix

MSTest.Acceptance.IntegrationTests.csproj — restore PackageReference ... ExcludeAssets="all" anchors (the kind Dependabot reads) for both Microsoft.Playwright.MSTest.v4 and Aspire.Hosting.Testing, while keeping the PackageDownload items for nupkg staging + *Version property correlation. Rewrote the comment to document the real Dependabot behavior. This dual-item layout is exactly what Aspire ran through green CI between Anchor SDK-bundled packages so Dependabot bumps them #9422 and Fix Dependabot discovery of bundled Playwright via PackageDownload #9452.
Directory.Packages.props — bump bundled Playwright 1.60.0 → 1.61.0 (both the MicrosoftPlaywrightVersion property and the literal Microsoft.Playwright.MSTest.v4PackageVersion, kept in sync so _ValidateBundledSdkFeatureVersions passes). Corrected the "condition 2" comment.

Verification

The change is config-only and structurally identical to the proven Aspire setup, so I'm confident in the MSBuild validity. The Dependabot behavior itself can only be confirmed on the next scheduled run against main.

#9452 switched the Dependabot anchor to PackageDownload, but Dependabot's NuGet ecosystem does not read PackageDownload items at all (dependabot/dependabot-core#2502), so the bundled Playwright version became invisible to Dependabot and stopped updating (1.61.0 was never proposed). Restore the PackageReference (ExcludeAssets="all") anchor for both Microsoft.Playwright.MSTest.v4 and Aspire.Hosting.Testing - ExcludeAssets only stops assets flowing into the build, it does not hide the reference from Dependabot. Keep the PackageDownload items for nupkg staging and property correlation. Bump bundled Playwright 1.60.0 -> 1.61.0. Fixes#9362 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot

Pull request overview

This PR adjusts how MSTest SDK–bundled packages are surfaced to Dependabot (so updates get proposed) and bumps the bundled Playwright version to 1.61.0.

Changes:

Restores PackageReference + ExcludeAssets="all" anchors (and keeps PackageDownload staging) for Playwright and Aspire in the MSTest acceptance integration test project.
Bumps MicrosoftPlaywrightVersion and the corresponding CPM PackageVersion for Microsoft.Playwright.MSTest.v4 from 1.60.0 to 1.61.0.
Updates in-file documentation to reflect Dependabot’s behavior and the intended anchor mechanism.

Show a summary per file

File	Description
test/IntegrationTests/MSTest.Acceptance.IntegrationTests/MSTest.Acceptance.IntegrationTests.csproj	Reintroduces Dependabot-visible `PackageReference` anchors while retaining `PackageDownload` entries used for nupkg staging.
Directory.Packages.props	Updates Playwright version to 1.61.0 and revises the “Dependabot discovery” guidance/comments for bundled SDK packages.

Review details

Files reviewed: 2/2 changed files
Comments generated: 1
Review effort level: Low

…isleading PackageDownload - Revert the manual 1.60.0 -> 1.61.0 bump: doing it here would leave the bundle at latest, so we couldn't tell whether the anchor fix actually let Dependabot propose the update. Leaving it at 1.60.0 means Dependabot's next run proposing 1.60.0 -> 1.61.0 is the proof the fix works. - Drop the Playwright PackageDownload anchor and its misleading comment (flagged in review): Dependabot ignores PackageDownload entirely, and nothing consumes Playwright's nupkg (only Aspire's is staged by CopyNuGetPackagesForTestAssets). The PackageReference (ExcludeAssets="all") is the sole Dependabot anchor; Aspire keeps its PackageDownload purely for nupkg staging. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Amaury Levé (Evangelink) · 2026-06-29T18:02:59Z

🧪 Test quality grade — PR #9508

No new or modified test methods were identified in the changed regions
of this PR. Nothing to grade.

_{Re-run with /grade-tests.}

🤖 Automated content by GitHub Copilot. Posted via a maintainer's GitHub token, so it appears under their account — the account owner did not write or approve this content personally. Generated by the Grade Tests on PR (on open / sync) workflow. · 123.4 AIC · ⌖ 12.5 AIC · ⊞ 43.8K · [◷]( · ◷)

Petr Pokorny (0101) · 2026-06-30T08:16:33Z

Heads-up: this diff doesn't appear to include the version bump described in the Fix section.

The description says it bumps bundled Playwright 1.60.0 → 1.61.0 in Directory.Packages.props (both the MicrosoftPlaywrightVersion property and the Microsoft.Playwright.MSTest.v4PackageVersion), but at the current head both still read 1.60.0:

Directory.Packages.props (~line 40): <MicrosoftPlaywrightVersion>1.60.0</MicrosoftPlaywrightVersion>
Directory.Packages.props (~line 177): <PackageVersion Include="Microsoft.Playwright.MSTest.v4" Version="1.60.0" />

The Directory.Packages.props hunks in the diff are limited to the comment block, and the PackageReference anchor restoration in MSTest.Acceptance.IntegrationTests.csproj looks correct. It just looks like the manual 1.61.0 edit didn't make it into the commits.

Could you double-check and push the version bump (so _ValidateBundledSdkFeatureVersions reflects it now rather than waiting on the next Dependabot run)? Alternatively, if this PR is meant to be the discovery-mechanism fix only, the title/description could be updated to match. Thanks!

Amaury Levé (Evangelink) · 2026-06-29T17:49:26Z

Fixes#9362

Problem

Despite several attempts (#9365, #9422, #9452), Dependabot still never bumps the bundled Playwright version. As reported in #9362, it's stuck at 1.60.0 even though Microsoft.Playwright.MSTest.v4 1.61.0 has been published on nuget.org for days across multiple daily Dependabot runs.

Root cause

#9452 switched the Dependabot anchor for the bundled packages from a PackageReference (with ExcludeAssets="all") to a PackageDownload, on the theory that ExcludeAssets="all" hid the reference from Dependabot.

That theory is wrong on both counts:

Dependabot's NuGet ecosystem does not read PackageDownload items at all (dependabot/dependabot-core#2502). So after Fix Dependabot discovery of bundled Playwright via PackageDownload #9452 the Playwright anchor became invisible to Dependabot.
ExcludeAssets="all" does NOT hide a PackageReference from Dependabot — it only stops the package's assets from flowing into the build. Dependabot reads the PackageReference XML node, not the asset-flow rules. So the original #9422 anchor was the correct mechanism.

Aspire's bump in #9446 actually came from its ExcludeAssetsPackageReference (present during the #9422–#9452 window), not from its PackageDownload. Playwright simply had no newer release during that brief window (1.61 wasn't out yet); then #9452 removed the working anchor right before 1.61 shipped — and silently broke Aspire's discovery too (it only looks fine because it's already at latest).

Fix

MSTest.Acceptance.IntegrationTests.csproj — restore PackageReference ... ExcludeAssets="all" anchors (the kind Dependabot reads) for both Microsoft.Playwright.MSTest.v4 and Aspire.Hosting.Testing, while keeping the PackageDownload items for nupkg staging + *Version property correlation. Rewrote the comment to document the real Dependabot behavior. This dual-item layout is exactly what Aspire ran through green CI between Anchor SDK-bundled packages so Dependabot bumps them #9422 and Fix Dependabot discovery of bundled Playwright via PackageDownload #9452.
Directory.Packages.props — bump bundled Playwright 1.60.0 → 1.61.0 (both the MicrosoftPlaywrightVersion property and the literal Microsoft.Playwright.MSTest.v4PackageVersion, kept in sync so _ValidateBundledSdkFeatureVersions passes). Corrected the "condition 2" comment.

Verification

The change is config-only and structurally identical to the proven Aspire setup, so I'm confident in the MSBuild validity. The Dependabot behavior itself can only be confirmed on the next scheduled run against main.

#9452 switched the Dependabot anchor to PackageDownload, but Dependabot's NuGet ecosystem does not read PackageDownload items at all (dependabot/dependabot-core#2502), so the bundled Playwright version became invisible to Dependabot and stopped updating (1.61.0 was never proposed). Restore the PackageReference (ExcludeAssets="all") anchor for both Microsoft.Playwright.MSTest.v4 and Aspire.Hosting.Testing - ExcludeAssets only stops assets flowing into the build, it does not hide the reference from Dependabot. Keep the PackageDownload items for nupkg staging and property correlation. Bump bundled Playwright 1.60.0 -> 1.61.0. Fixes#9362 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot

Pull request overview

This PR adjusts how MSTest SDK–bundled packages are surfaced to Dependabot (so updates get proposed) and bumps the bundled Playwright version to 1.61.0.

Changes:

Restores PackageReference + ExcludeAssets="all" anchors (and keeps PackageDownload staging) for Playwright and Aspire in the MSTest acceptance integration test project.
Bumps MicrosoftPlaywrightVersion and the corresponding CPM PackageVersion for Microsoft.Playwright.MSTest.v4 from 1.60.0 to 1.61.0.
Updates in-file documentation to reflect Dependabot’s behavior and the intended anchor mechanism.

Show a summary per file

File	Description
test/IntegrationTests/MSTest.Acceptance.IntegrationTests/MSTest.Acceptance.IntegrationTests.csproj	Reintroduces Dependabot-visible `PackageReference` anchors while retaining `PackageDownload` entries used for nupkg staging.
Directory.Packages.props	Updates Playwright version to 1.61.0 and revises the “Dependabot discovery” guidance/comments for bundled SDK packages.

Review details

Files reviewed: 2/2 changed files
Comments generated: 1
Review effort level: Low

…isleading PackageDownload - Revert the manual 1.60.0 -> 1.61.0 bump: doing it here would leave the bundle at latest, so we couldn't tell whether the anchor fix actually let Dependabot propose the update. Leaving it at 1.60.0 means Dependabot's next run proposing 1.60.0 -> 1.61.0 is the proof the fix works. - Drop the Playwright PackageDownload anchor and its misleading comment (flagged in review): Dependabot ignores PackageDownload entirely, and nothing consumes Playwright's nupkg (only Aspire's is staged by CopyNuGetPackagesForTestAssets). The PackageReference (ExcludeAssets="all") is the sole Dependabot anchor; Aspire keeps its PackageDownload purely for nupkg staging. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Amaury Levé (Evangelink) · 2026-06-29T18:02:59Z

🧪 Test quality grade — PR #9508

No new or modified test methods were identified in the changed regions
of this PR. Nothing to grade.

_{Re-run with /grade-tests.}

🤖 Automated content by GitHub Copilot. Posted via a maintainer's GitHub token, so it appears under their account — the account owner did not write or approve this content personally. Generated by the Grade Tests on PR (on open / sync) workflow. · 123.4 AIC · ⌖ 12.5 AIC · ⊞ 43.8K · [◷]( · ◷)

Petr Pokorny (0101) · 2026-06-30T08:16:33Z

Heads-up: this diff doesn't appear to include the version bump described in the Fix section.

The description says it bumps bundled Playwright 1.60.0 → 1.61.0 in Directory.Packages.props (both the MicrosoftPlaywrightVersion property and the Microsoft.Playwright.MSTest.v4PackageVersion), but at the current head both still read 1.60.0:

Directory.Packages.props (~line 40): <MicrosoftPlaywrightVersion>1.60.0</MicrosoftPlaywrightVersion>
Directory.Packages.props (~line 177): <PackageVersion Include="Microsoft.Playwright.MSTest.v4" Version="1.60.0" />

The Directory.Packages.props hunks in the diff are limited to the comment block, and the PackageReference anchor restoration in MSTest.Acceptance.IntegrationTests.csproj looks correct. It just looks like the manual 1.61.0 edit didn't make it into the commits.

Could you double-check and push the version bump (so _ValidateBundledSdkFeatureVersions reflects it now rather than waiting on the next Dependabot run)? Alternatively, if this PR is meant to be the discovery-mechanism fix only, the title/description could be updated to match. Thanks!

CopilotAI review requested due to automatic review settings June 29, 2026 17:49

Amaury Levé (Evangelink) mentioned this pull request Jun 29, 2026
Update bundled Playwright for .NET version in MSTest SDK #9362
Closed

Copilotstarted reviewing on behalf of Amaury Levé (Evangelink)June 29, 2026 17:49 View session

CopilotAI reviewed Jun 29, 2026
View reviewed changes

Comment thread...ntegrationTests/MSTest.Acceptance.IntegrationTests/MSTest.Acceptance.IntegrationTests.csproj Outdated

This comment has been minimized.
Sign in to view

Amaury Levé (Evangelink) added the state/needs-review Awaiting review from the team. label Jun 29, 2026

Amaury Levé (Evangelink) enabled auto-merge (squash) June 29, 2026 19:10

Artur Spychaj (drognanar) approved these changes Jun 30, 2026
View reviewed changes

Amaury Levé (Evangelink) merged commit 51edbf7 into mainJun 30, 2026
39 checks passed

Amaury Levé (Evangelink) deleted the dev/amauryleve/jubilant-parakeet branch June 30, 2026 08:39

Amaury Levé (Evangelink) mentioned this pull request Jul 7, 2026
Add scheduled workflow to bump bundled Playwright (fixes #9362) #9666
Merged

CopilotAI mentioned this pull request Aug 25, 2026
Avoid restoring SDK dependency anchors in CI #10741
Merged