Release 0.12.1 - #5
Merged
Merged
Conversation
Four fixes, all downstream of one rule: a name is not an identity. Also repairs the CHANGELOG link block, which still compared Unreleased against v0.11.0 and had no entry for 0.12.0 at all. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Cuts 0.12.1 — four fixes, no new surface, nothing breaking.
What ships
DbSet<T>registrationpartialclass is one entity, not one per fileDbContext's own properties count as registrationsVersion claims
Every place the version is written by hand, moved together:
Directory.Build.props, the README'sstatus line, the plugin manifest, the skill front matter, and
.mcp/server.json.StatesTheSameVersionEverywhereItIsWrittencaught the last of those after I had already convincedmyself I had found them all — the test exists because these five have drifted before, and it earned
its keep again today.
.mcp/server.jsonwas edited as bytes to keep it free of a byte order mark, which nuget.orgrejects the package for.
Also repaired
The CHANGELOG link block still compared
[Unreleased]against v0.11.0 and had no[0.12.0]entry at all — 0.12.0 shipped without it being updated. Both fixed here.
Not in this PR
Publishing. Merging this only puts the version on
main; the packages go out when a GitHub Releaseis created, which fires
nuget.ymlandmcp-registry.yml. A NuGet version number cannot be reusedonce it is taken, so that stays a deliberate, separate act.
Verification