Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

update-roslyn-version

Sterne1

Forks0

Aktualisiert25. Februar 2026 um 02:48

Update all Roslyn dependency versions in the razor repository. Use this when asked to update, bump, or change the Roslyn version.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

AKJUS

AKJUS/razor

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	update-roslyn-version
description	Update all Roslyn dependency versions in the razor repository. Use this when asked to update, bump, or change the Roslyn version.

Update Roslyn Version

Update all Roslyn dependency versions in the razor repository. The user will provide the new version number (e.g. 5.5.0-2.26118.1).

Steps

Identify the current Roslyn version by reading eng/Version.Details.xml — look at the Version attribute on any <Dependency> element with <Uri>https://github.com/dotnet/roslyn</Uri>.
Update eng/Version.Details.props: Replace all Roslyn package version values (in the  section) with the new version. These are the *PackageVersion elements. The old value may be a -dev placeholder or a full version string.
Update eng/Version.Details.xml: Replace all Roslyn <Dependency> elements' Version attributes with the new version.
Run restore.cmd (or restore.sh on non-Windows) from the repo root to download the new packages. Wait for it to complete successfully.
Get the commit hash: After restore, find a .nuspec file for one of the restored Roslyn packages in the NuGet cache (D:\NugetCache on this machine). For example:
```
D:\NugetCache\microsoft.codeanalysis.common\<NEW_VERSION>\microsoft.codeanalysis.common.nuspec
```
Parse the <repository commit="..."> element from the nuspec to extract the commit SHA. All Roslyn packages share the same commit.
Update the commit SHA in eng/Version.Details.xml: Replace the old Roslyn <Sha> values with the new commit hash from step 5. Only update Roslyn entries (those with <Uri>https://github.com/dotnet/roslyn</Uri>), not arcade/aspnetcore/runtime entries.
Verify by running git diff to confirm only the expected version and SHA changes were made in the two files.

Notes

Do NOT modify non-Roslyn dependencies (arcade, aspnetcore, runtime).
The NuGet cache path may vary by machine. Common locations:
- Windows: D:\NugetCache or %USERPROFILE%\.nuget\packages
- macOS/Linux: ~/.nuget/packages
If restore fails, the version may not exist on the configured NuGet feeds — verify the version string.

Mehr aus diesem Repository

gleiches Repository

formatting-log

AKJUS/razor

Import Razor formatting log zips that the user has already downloaded from Azure DevOps feedback tickets or GitHub issues into FormattingLogTest, validate whether the captured problem still reproduces, and if needed drive a minimal repro plus fix workflow.

2026-04-071

run-toolset-tests

AKJUS/razor

Run the razor-toolset-ci pipeline to validate the current branch against large third-party repositories (MudBlazor, OrchardCore, ASP.NET Core, etc.). Use when asked to run toolset tests, ecosystem tests, or third-party validation.

2026-03-191

ci-analysis

AKJUS/razor

Analyze CI build and test status from Azure DevOps and Helix for dotnet repository PRs. Use when checking CI status, investigating failures, determining if a PR is ready to merge, or given URLs containing dev.azure.com or helix.dot.net. Also use when asked "why is CI red", "test failures", "retry CI", "rerun tests", "is CI green", "build failed", "checks failing", or "flaky tests".

2026-03-091

code-review

AKJUS/razor

Review code changes in dotnet/razor for correctness, performance, and consistency with project conventions. Use when reviewing PRs or code changes.

2026-03-091

vmr-codeflow-status

AKJUS/razor

Analyze VMR codeflow PR status for dotnet repositories. Use when investigating stale codeflow PRs, checking if fixes have flowed through the VMR pipeline, debugging dependency update issues in PRs authored by dotnet-maestro[bot], checking overall flow status for a repo, or diagnosing why backflow PRs are missing or blocked.

2026-03-091

Update Roslyn Version

Update all Roslyn dependency versions in the razor repository. The user will provide the new version number (e.g. 5.5.0-2.26118.1).

Steps

Identify the current Roslyn version by reading eng/Version.Details.xml — look at the Version attribute on any <Dependency> element with <Uri>https://github.com/dotnet/roslyn</Uri>.

Update eng/Version.Details.props: Replace all Roslyn package version values (in the  section) with the new version. These are the *PackageVersion elements. The old value may be a -dev placeholder or a full version string.

Update eng/Version.Details.xml: Replace all Roslyn <Dependency> elements' Version attributes with the new version.

Run restore.cmd (or restore.sh on non-Windows) from the repo root to download the new packages. Wait for it to complete successfully.

Get the commit hash: After restore, find a .nuspec file for one of the restored Roslyn packages in the NuGet cache (D:\NugetCache on this machine). For example:

D:\NugetCache\microsoft.codeanalysis.common\<NEW_VERSION>\microsoft.codeanalysis.common.nuspec

Parse the <repository commit="..."> element from the nuspec to extract the commit SHA. All Roslyn packages share the same commit.

Update the commit SHA in eng/Version.Details.xml: Replace the old Roslyn <Sha> values with the new commit hash from step 5. Only update Roslyn entries (those with <Uri>https://github.com/dotnet/roslyn</Uri>), not arcade/aspnetcore/runtime entries.

Verify by running git diff to confirm only the expected version and SHA changes were made in the two files.

Notes

Do NOT modify non-Roslyn dependencies (arcade, aspnetcore, runtime).

The NuGet cache path may vary by machine. Common locations:

Windows: D:\NugetCache or %USERPROFILE%\.nuget\packages
macOS/Linux: ~/.nuget/packages

If restore fails, the version may not exist on the configured NuGet feeds — verify the version string.