[v4] Update package versions - #5139
Open
Denis Voituron (dvoituron) wants to merge 3 commits into
Open
Conversation
Denis Voituron (dvoituron)
requested a review
from Vincent Baaij (vnbaaij)
as a code owner
August 12, 2026 11:35
This was referenced Aug 12, 2026
Copilot started reviewing on behalf of
Denis Voituron (dvoituron)
August 12, 2026 11:35
View session
This was referenced Aug 12, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Updates dependency versions (NuGet central package versions and Core.Assets npm tooling deps) and adds a repository script to report outdated NuGet/npm packages, aiming to simplify ongoing maintenance for the Fluent UI Blazor solution.
Changes:
- Bump
@typescript-eslint/*(and related lockfile entries) insrc/Core.Assets. - Update several centrally-managed NuGet package versions and shared version properties in
Directory.Packages.props. - Add
_ListOutdatedDependencies.ps1to generate a grouped report of outdated NuGet and npm packages without modifying manifests.
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| src/Core.Assets/package.json | Updates TypeScript ESLint dev dependency versions. |
| src/Core.Assets/package-lock.json | Regenerates lockfile entries to match updated npm package versions. |
| Directory.Packages.props | Updates centrally managed NuGet package versions and shared framework version properties. |
| _ListOutdatedDependencies.ps1 | Adds a helper script to report outdated NuGet and npm dependencies. |
Files not reviewed (1)
- src/Core.Assets/package-lock.json: Generated file
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
✅ All tests passed successfully Details on your Workflow / Core Tests page. |
Summary - Unit Tests Code CoverageSummary
CoverageMicrosoft.FluentUI.AspNetCore.Components - 61.3%
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[v4] Update package versions
Introduce a script that identifies outdated NuGet and npm packages across the solution, enhancing maintenance and upgrade processes. Update package versions to improve stability and compatibility. This change does not introduce breaking changes.
Note
AngleSharp.CSS 1.0.1 required AngleSharp >= 1.5.0, which forced NuGet to bump the transitive AngleSharp package from 1.2.0 (the version bunit.web 1.40.0 was compiled against) to 1.5.0. Since Bunit.Web.dll's RefreshableElementCollection was compiled against AngleSharp 1.2.0's IHtmlCollection indexer, loading the newer incompatible AngleSharp 1.5.0 at runtime caused a MissingMethodException.
Fix: pinned the central AngleSharp.CSS package version in Directory.Packages.props down to 1.0.0-beta.154 (resolved to 1.0.0-beta.157), which keeps the transitive AngleSharp core package at 1.2.0, matching what bUnit expects. Verified the previously failing test FluentWizard_NavigateNext now passes, and the test project builds successfully.