Bump Weasel 9.23.0 → 9.23.1 - #5124
Merged
Merged
Conversation
weasel#420 + weasel#422: the identifier validation added for weasel#416 now covers every provider migrator instead of PostgreSQL alone, and PostgreSQL's own copy is folded onto the shared Weasel.Core helper so the providers cannot drift apart again. SQL Server previously validated nothing at all; Oracle, MySQL and Sqlite each missed their own quoting characters. Marten only consumes the PostgreSQL side, so this is a hardening roll-forward rather than a fix for a Marten-reachable hole -- 9.23.0 already carried the PostgreSQL check that GHSA-3vp4-34pf-2rcw's class needs, and 9.21.1 carries the partition-bound VALUES escaping. Kept as its own commit rather than riding along with #5123, because a Weasel bump has form for landing outside the area it looks like it touches: 9.18-9.20.1 broke Bug_4614 in CoreTests through MatchesForDelta, nowhere near the release note. Verified net9.0 against the published package on that history: - CoreTests 519/0/1 (the project that caught the 9.18-9.20.1 regression) - DocumentDbTests 1089/0/1 - EventSourcingTests 1613/0/7 - TenantPartitionedEventsTests 238/0/2 (identifier validation is closest to the partition naming paths) Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VpDCvJcBDZerieJB4JEHde
jeremydmiller
force-pushed
the
chore/weasel-9.23.1
branch
from
August 2, 2026 17:21
d193ec0 to
0560165
Compare
This was referenced Aug 4, 2026
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.
Rolls Weasel forward to 9.23.1 —
Weasel.Postgresql,Weasel.Storage,Weasel.EntityFrameworkCore.What's in it
weasel#420 + weasel#422: the identifier validation added for weasel#416 now covers every provider migrator instead of PostgreSQL alone, and PostgreSQL's own copy is folded onto the shared
Weasel.Corehelper so the providers cannot drift apart again. SQL Server previously validated nothing at all; Oracle, MySQL and Sqlite each missed their own quoting characters.Marten only consumes the PostgreSQL side, so this is a hardening roll-forward, not a fix for a Marten-reachable hole: 9.23.0 already carried the PostgreSQL check that the GHSA-3vp4-34pf-2rcw class needs, and 9.21.1 carries the partition-bound
VALUESescaping. Worth taking anyway to stay on the current line.Why it's a separate PR
A Weasel bump has form for landing outside the area it looks like it touches. Weasel 9.18–9.20.1 broke
Bug_4614throughMatchesForDeltabypassing a subclassEquals(object)— nowhere near anything in the release notes. Keeping it off #5123 means a bisect lands on one changed line.Verification
net9.0, against the published package, on this history (no other changes):
🤖 Generated with Claude Code
https://claude.ai/code/session_01VpDCvJcBDZerieJB4JEHde