Bump Weasel 9.23.0 → 9.23.1 - #405
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. This is the directly relevant half for Polecat: the SQL Server migrator previously validated NOTHING at all. Oracle, MySQL and Sqlite each missed their own quoting characters and were fixed in the same pass. Pairs with #403, which escaped Polecat's own interpolated identifiers and literals -- that closed the call sites, this closes the layer underneath them. Full suite net9.0: 1657/0/3, identical to the same-day main baseline. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VpDCvJcBDZerieJB4JEHde
Merged
jeremydmiller
added a commit
that referenced
this pull request
Aug 3, 2026
Minor rather than patch: 5.9.1's line added public surface (IEventBinarySerializer, EventStoreOptions.AddEventType/AddEventTypes) and moved the whole JasperFx/Weasel matrix forward. Since 5.9.1: - feat: pluggable binary event serialization via IEventBinarySerializer (#388/#402) - feat: EventStoreOptions.AddEventType / AddEventTypes (#395/#396) - fix: escape interpolated identifiers and literals in constructed SQL (#390/#403) - fix: throw a lone DcbConcurrencyException unwrapped from SaveChangesAsync (#394/#397) - deps: JasperFx 2.37.2 -> 2.38.0, Weasel 9.23.0 -> 9.23.2 (#405, #407) - Polecat's ProjectionScenario is now a thin subclass of the lifted JasperFx.Events.TestSupport harness rather than a seven-file copy of Marten's (#404/#408, jasperfx#616) -- a behavior change for anyone already using it, see the release notes - test infrastructure: compliance waves 1-3 (#393, #400, #407), parallel-safe test suite (#389), IntegrationContext.StoreOptions document cleaning (#398/#401)
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.SqlServer,Weasel.Storage,Weasel.EntityFrameworkCore.What's in it, and why Polecat cares more than Marten does
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.The SQL Server migrator previously validated nothing at all. That is the directly relevant half for Polecat — Marten already had its check in 9.23.0 and takes this bump as hardening only. Oracle, MySQL and Sqlite each missed their own quoting characters and were fixed in the same pass.
Pairs naturally with #403, which escaped Polecat's own interpolated identifiers and literals: that closed the call sites, this closes the layer underneath them.
Verification
Full suite net9.0: 1657 / 0 / 3 — identical to the same-day
mainbaseline, so the bump moves nothing.Kept as its own PR because a Weasel bump has form for landing outside the area it looks like it touches (Weasel 9.18–9.20.1 broke a Marten regression test through
MatchesForDelta, nowhere near its release notes). One changed file means a bisect lands on one line.🤖 Generated with Claude Code
https://claude.ai/code/session_01VpDCvJcBDZerieJB4JEHde