Skip to content

Clear vulnerable transitive packages in test project; update CI - #8

Merged
jonhilt merged 1 commit into
mainfrom
focus/can-we-check-https-1-fea0
Oct 27, 2026
Merged

jonhilt merged 1 commit into
mainfrom
focus/can-we-check-https-1-fea0

Conversation

@jonhilt

@jonhilt jonhilt commented Oct 27, 2026

Copy link
Copy Markdown
Contributor

dotnet list package --vulnerable --include-transitive flagged two High severity advisories, both in the test project only (not the published package):

Both came in through NETStandard.Library 1.6.1 via xunit 2.4.2 and FakeItEasy 7.4.0.

Changes:

  • Test project: net6.0 → net8.0; xunit 2.9.3, xunit.runner.visualstudio 3.1.5, Microsoft.NET.Test.Sdk 18.11.0, FakeItEasy 9.0.1, coverlet.collector 6.0.4
  • CI and release workflows: .NET 8 SDK (needed for the net8.0 tests; it still builds the net6.0 library), actions/checkout v2 → v4

The library itself still targets net6.0 and its packages are unchanged; it scans clean.

Verified locally: vulnerability scan is clean for both projects, and all 7 tests pass.

The test project pulled System.Net.Http 4.3.0 and System.Text.RegularExpressions
4.3.0 (both High severity advisories) through old xunit and FakeItEasy versions.
Moves the test project to net8.0 with current test packages, and updates CI to
the .NET 8 SDK and actions/checkout@v4. The published library still targets net6.0.
@jonhilt

jonhilt commented Oct 27, 2026

Copy link
Copy Markdown
Contributor Author

🔍 QA report: ✅ Passed

Tested at commit eedd2f2

The PR does what it says. The test project moves to net8.0 with newer test packages, and CI and release use the .NET 8 SDK with checkout v4. All 7 tests pass, and the vulnerability scan is clean for both projects. I found no proof-worthy problems.

Check Details
✅ Vulnerable transitive packages cleared dotnet list package --vulnerable --include-transitive reports no vulnerable packages for both the library and the test project.
✅ Tests pass on net8.0 dotnet test ran 7 passed, 0 failed on net8.0. The only new warning is xUnit1012, which flags a null passed to a non-nullable string parameter in an existing test.
✅ Library unchanged and still builds on net6.0 The library csproj is untouched and still targets net6.0. It built with the newer SDK, producing bin/Debug/net6.0.
✅ Workflow edits ci.yml and release.yml change only the checkout version (v2 to v4) and the .NET SDK version (6.0.x to 8.0.x). The release.yml YAML indentation is preserved. Build.ps1 needs no change because it is SDK-agnostic. I could not run the workflows themselves locally.
✅ Edge: SDK to library target compatibility The .NET 8 SDK can build a net6.0 target, and the net6.0 targeting pack restores from NuGet. There is no global.json pinning an SDK.
🧪 Commands run
Command Result
dotnet test (test project) 7 passed, 0 failed
dotnet list package --vulnerable --include-transitive no vulnerable packages in either project

🔦 Worth a human look

  • .github/workflows/ci.yml:23: The workflows were not run here. Confirm CI passes on the windows-latest runner with the .NET 8 SDK building the net6.0 library.

📂 Files reviewed

2 of 2 changed code files opened by QA (from its tool calls) · 2 code files with no test

Each file
File Opened Tests What QA checked
.github/workflows/ci.yml ✅ ⚠️ none (CI config) Read the diff: checkout v4 and .NET 8 SDK. It is consistent with the test project's net8.0 target.
.github/workflows/release.yml ✅ ⚠️ none (CI config) Read the diff: the same changes as ci.yml, with indentation preserved.
src/Tailwind.Extensions.AspNetCore.Tests/Tailwind.Extensions.AspNetCore.Tests.csproj – All 7 existing tests Read the diff: target framework and package versions bumped. The restore, build and tests ran, and the vulnerability scan is clean.

📸 Screenshots

No screenshots were taken during this review.

@jonhilt
jonhilt added this pull request to stack #11 October 27, 2026 14:00
@jonhilt
jonhilt merged commit 014a696 into main Oct 27, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant