Repository navigation
chore: carry the 10.4.0 sections to main (#519) - #523
Merged
Merged
Conversation
The five [10.4.0] changelog sections, verbatim from v10.4.0; a "Changed answers in 10.4.0" section in docs/migration.md linking the three subsections under Migration from v10.x that the 10.4.0 changelog's rows point at; PackageValidationBaselineVersion, the SECURITY.md rows and the walkthrough sample move to 10.4.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CaffeinatedCoder
added
chore
CaffeinatedCoder
enabled auto-merge
October 26, 2026 18:47
Closed
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.
Closes #519
Problem
This is step 5 of #519, after
v10.4.0shipped: the tag is on 88a1628, all four packages are on nuget.org, and the GitHub release is Latest.mainkeeps the sections of every release on both lines, but it has no 10.4.0 changelog sections yet. The v10.4.0 notes link toblob/main/docs/migration.md#changed-answers-in-1040, which doesn't exist onmain.Change
## [10.4.0] — 2026-10-26section, copied verbatim fromv10.4.0, between11.0.0-preview.1and10.3.0.docs/migration.md: a short## Changed answers in 10.4.0section that links the three subsections already under## Migration from v10.x, as chore: carry the 10.3.0 sections to main (#470) #474 did for 10.3.0: string set collations (Text value set operators follow a nondeterministic column collation: on a case-insensitive column, Contains("a") is true for {A} and Remove("a") deletes A #483, A case-insensitive collation on the element side still makes string set Contains and Remove compare case-insensitively #507), date bounds at an exclusive infinity (LowerBound(), UpperBound() and Clamp in a query read a date range another tool wrote with an exclusive infinite bound one day wider than memory loads it #489) andYearMonthRangeupper bounds (YearMonthRange Clamp and UpperBound() in a filter compare as the month's last day, so == against the month is false #506). Those subsections already say "Before 10.4.0", and the v10.x intro already says the last four items shipped in 10.4.0, so nothing else moves.Directory.Build.props:PackageValidationBaselineVersionmoves from 10.3.0 to 10.4.0.SECURITY.md: the rows become10.4.x ✅and< 10.4 ❌.samples/Bookings/Bookings.csproj: the package version moves to 10.4.0, along with the baseline.Tests
--no-http-cache).dotnet pack -c Releasevalidates all four packages against the 10.4.0 baseline without errors.main.🤖 Generated with Claude Code