Repository navigation
docs: 10.0.0 release notes — stored 24:00 timerange bounds, migration order - #247
Merged
Merged
Conversation
PostgreSQL's time holds 24:00:00 and TimeOnly doesn't. The docs told a writer what to use instead but not what happens to a row another tool wrote: Npgsql's time read throws ArgumentOutOfRangeException on load and on a projected bound. The note gives the UPDATE that rewrites such rows to an unbounded end; claim E62 is held by a live test of both the failure and the remedy. Closes #108 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs/migration.md runs from the oldest major a reader migrates from to the newest; the 10.0.0 work had put v9.x above v8.x. A convention test now holds the order, so the 10.x and 11.x sections land in place. Also names the integration test project in dependabot.yml's note on the crypto packages EF Core Design pulls in: CompiledModelJsonTests (#43) added the same reference there. Closes #201 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CaffeinatedCoder
added
documentation
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.
Closes #108
Closes #201
Problem
TimeOnlyhas no24:00:00, but not what happens to a row another tool wrote with one. Npgsql'stimeread throws on load and on a projected bound.dependabot.yml's note on theSystem.Security.Cryptography.*packages named only one of the two test projects that reference EF Core Design. test: round-trip every type in a JSON column through a compiled model #211 (Test JSON-column readers and writers through a compiled model #43) added it to the integration tests, which is where the 13 open alerts come from.Change
timerange: a stored24:00:00bound throwsArgumentOutOfRangeExceptionfrom Npgsql'stimeread when the row loads or the bound is projected. Rewrite such rows withtimerange(lower(x), NULL). Claim E62.ChangelogConventionTests.MigrationSections_RunFromTheOldestMajorToTheNewestholds the order..github/dependabot.yml: the comment names both projects. No ignore rule changes.I audited the 10.0.0 changelog section against everything merged under #58 today. Breaking lists the PostgreSQL 16 floor, the integer NUL refusal (#233) and the ISO-only
DateTimeOffsetoffsets (#234), and the v9.x migration list links each one, so nothing needed adding. The release date still says 2026-10-17. It's set to the tag date when tagging.Tests
TimeAndYearMonthIntegrationTests.TimeRange_AStored2400Bound_ThrowsOnLoad_AndTheDocumentedRemediesLoad(live PostgreSQL): it passes, and it fails with the stored value changed to23:00.v1.x … v7.x, v9.x, v8.x).🤖 Generated with Claude Code