Repository navigation
Conversation
Both sides were provider specs, strings such as previous-nuget|MyLib|1.3.0 split on pipes, with flags shared by every source. release, files, nuget and github now take typed arguments and share -t, -f, -o and --fail-on; release reads the package id and version from a .nupkg, and files and release compare .nupkg files on the newest framework both sides ship. diff runs the same comparison, hidden from help, so existing builds keep working. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Mpdreamz
added a commit
that referenced
this pull request
Nov 14, 2026
Run without a command in a repository, assembly-differ now compares every library project's Release build with the latest release of its package. It skips test projects and projects that are not packable, and it does not build. **Prompt summary:** Running assembly-differ without arguments, in a directory with a solution or project file, should report the changes by itself. That makes it easy for people and coding agents alike. It skips test projects and `IsPackable=false` projects, each of which a flag includes, and a project flag picks projects. Building is left to the user, with a warning when there is no build output. The `--build` orchestration of the `github` command is the tool doing too much, so it goes. ## Why To see what a change does to a library's API, a person or an agent had to know the package id, the last version, the target framework and where the build output lives, then spell all of it out. An agent checking a change usually decompiled the assemblies itself instead. ## What #### `projects`, the default command The command reads the one `.slnx` or `.sln` in the directory through `dotnet sln list`, or else its project files. It asks MSBuild for `IsPackable`, `IsTestProject`, `PackageId`, `AssemblyName` and the target frameworks. For the newest framework, it finds the Release `TargetPath` and compares it with the latest stable release of the package on the NuGet.config feeds. Every project goes into one report. Each skipped project gets a line saying why and which flag includes it. A package with no release, or one that ships no matching assembly, such as a tool package, is reported and skipped. #### No building The tool does not build. A project without Release output is skipped with a warning that says to run `dotnet build -c Release`. `--project` picks project files explicitly, whatever kind they are. Two provider specs passed straight to the root, as before commands existed, are routed to `diff`, so those callers still work. #### `github` command dropped, `github|` spec deprecated The `github` command cloned another commit and ran a build command the user had to spell out; it merged in [#75](#75) and was never released. The `github|...` spec in the hidden `diff` still works and now warns on stderr. The README shows the replacement: `git worktree add`, `dotnet build`, then `assembly-differ files`. #### A crash fixed A package with no assemblies under `lib/`, such as one that only ships an analyzer, crashed the NuGet provider with "Sequence contains no elements". It now reports that and compares nothing. ## Verify ```bash mise run test # ProjectsTests build a small solution for real: a library with a release on a local feed, a test project and an unpackable one cd ~/Projects/argh && dotnet build -c Release && dotnet run --project <assembly-differ checkout>/src/assembly-differ -f net11.0 -c Release ``` 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <[email protected]>
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.
assembly-differ now has a command per source:
release,files,nugetandgithub. Each takes typed arguments and the shared options-t,-f,-oand--fail-on.diffand its provider specs still work unchanged, hidden from help.Prompt summary: The tool is being dusted off. Two strings split on
|, with every flag shared by every source, are hard to read and hard to get right. argh can do better by making each source a proper subcommand. Existing callers must not break, so the currentdiffstays and is hidden.Why
Every comparison was
diff "<provider>|<arg>|<arg>" "<provider>|<arg>". The help could not say which parts a provider takes, a typo surfaced as an exception, and a CI build had to repeat the package id and version it had just packed.--helplisted one command whose usage was spread over a single parameter description.What
A command per source
release <path>compares a build with the release before it on nuget.org. Given a.nupkg, it reads the package id and version from it, soassembly-differ release build/output/MyLib.1.3.0.nupkgis the whole command.files <old> <new>takes a.dll, a directory or a.nupkgon each side.nuget <id> <old> <new>compares two published versions.githubbuilds an older commit with the command you give. Each has its own--help, with examples.Packages as input
A new provider reads a
.nupkgand unpacks the assemblies of one target framework.--frameworkpicks it. By default,filesandreleasetake the newest framework both sides ship, preferring .NET over .NET Standard over .NET Framework, and fail with a message when they share none.Shared options
-t,-f,-oand--fail-oncome from one[AsParameters]class, and argh validates--formatand--fail-onagainst their allowed values. The default format of the commands ismarkdown;diffkeepsxml.--fail-onstays a string until an argh release carries the enum default fix from nullean/argh#151.diffunchangedThe comparison moved into
DiffRunner, whichdiffand the commands share.diffis[Hidden], still the default command, and every characterization snapshot is unchanged. The root help describes the tool and lists the new commands.Docs
Both READMEs lead with the commands and keep a short section on provider specs. They also correct two claims: a provider spec without
diffworks, and Proc 0.13.0 marksNoWrapInThreadobsolete; it does not add it.Verify
Out of scope:
releasestill fails when no earlier release exists. The next pull request resolves the baseline, including a first release.action.ymlstill callsdiff; the action gets its own pull request.🤖 Generated with Claude Code