-
Notifications
You must be signed in to change notification settings - Fork 378
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: dotnet/arcade
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: aa61e8c20a
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: dotnet/arcade
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 086a177187
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 9 commits
- 20 files changed
- 8 contributors
Commits on Apr 23, 2025
-
Configuration menu - View commit details
-
Copy full SHA for dfb2c6d - Browse repository at this point
Copy the full SHA dfb2c6dView commit details
Commits on Apr 25, 2025
-
Configuration menu - View commit details
-
Copy full SHA for bfbc858 - Browse repository at this point
Copy the full SHA bfbc858View commit details
Commits on May 5, 2025
-
Configuration menu - View commit details
-
Copy full SHA for dba2627 - Browse repository at this point
Copy the full SHA dba2627View commit details -
[release/9.0] Update NuGetRepack to only update version of dependenci…
…es from the build (#15811) Since merging roslyn-analyzers into the roslyn repo, Roslyn packages have been generated that include a dependency on Microsoft.CodeAnalysis.Analyzers (a roslyn-analyzer package) with the wrong version. The packages should depend on version 3.11.0 of the M.CA.Analyzers package but the nuspec is being rewritten to require a M.CA.Analyzers package from the same build. This behavior is due to NuGetRepack only using the package name to determine whether to update a dependency version. This PR additionally validates that the dependency version is from the current build prior to updating. Co-authored-by: Joey Robichaud <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 1cfa39f - Browse repository at this point
Copy the full SHA 1cfa39fView commit details
Commits on May 13, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 9ee057b - Browse repository at this point
Copy the full SHA 9ee057bView commit details -
Configuration menu - View commit details
-
Copy full SHA for ac63dcf - Browse repository at this point
Copy the full SHA ac63dcfView commit details -
Configuration menu - View commit details
-
Copy full SHA for 93823d4 - Browse repository at this point
Copy the full SHA 93823d4View commit details
Commits on May 16, 2025
-
Configuration menu - View commit details
-
Copy full SHA for c62eeb5 - Browse repository at this point
Copy the full SHA c62eeb5View commit details
Commits on May 21, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 086a177 - Browse repository at this point
Copy the full SHA 086a177View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff aa61e8c20a...086a177187