richlander

Answer .NET release lifecycle, timeline, patch, and CVE questions by driving the public `dotnet-release` CLI over the release-index graph.

Update per-distro package files in release-notes/<version>/distros/ documenting dependencies and .NET package availability for each Linux distribution.

Audit and update os-packages.json files in dotnet/core to ensure Linux distribution package names are correct. Verifies package names against upstream package repositories and fixes mismatches.

Audit and update supported-os.json files in dotnet/core to reflect current OS version support. Uses release-notes verify for automated checking against upstream lifecycle data.

Build, install, list, and remove .NET tools using dotnet-install.

Build, install, list, and remove .NET tools using dotnet-install.

Publishing and release workflow for dotnet-install. Version bumps, CI, NuGet publish, GitHub Releases.

Query .NET APIs across NuGet packages, platform libraries, and local files. Use for factual answers about package contents, API signatures, compatibility changes, relationships, SourceLink, and assembly metadata.

Build, install, list, and remove .NET tools using dotnet-install.

Query .NET APIs across NuGet packages, platform libraries, and local files. Use for factual answers about package contents, API signatures, compatibility changes, relationships, SourceLink, and assembly metadata.

Analyze music listening data across Last.fm, YouTube, and Discogs. Run queries to find listening stats, discover new artists, identify strange absences, track surging interests, and build playlists from cross-source analysis.

Use dotnet-scope to diagnose .NET build errors. When a dotnet build fails, pipe the output to `dotnet-scope diagnose` to get enriched diagnostics with source context, documentation links, and suggestions for common errors like typos in method names.