Skip to content

Expand the README upgrade note into a guide covering 1.4.1 to 1.6 - #60

Merged
ademar merged 1 commit into
masterfrom
docs/upgrading-guide
Sep 25, 2026
Merged

ademar merged 1 commit into
masterfrom
docs/upgrading-guide

Conversation

@ademar

@ademar ademar commented Sep 25, 2026

Copy link
Copy Markdown
Member

Summary

The README's "Upgrading to 1.5" section becomes an Upgrading guide, newest release first:

  • 1.6: dates are returned in UTC.
    • The RFC sections behind the change, and the affected properties (DomainRenewResponse.ExDate and the four Nominet dates).
    • How unmarked values are treated.
    • A code sample for displaying (ToLocalTime()) and comparing (DateTime.UtcNow) the values.
    • Notes that string date properties are unchanged, and that DomainRenew now accepts an exDate directly.
  • 1.5: server certificates are validated. The existing section, unchanged apart from its heading.
  • 1.4.1: TLS version chosen by the operating system. Callers need to rebuild to pick up the new default, since C# compiles default values into call sites. Drop any explicit SslProtocols.Tls.

Testing

I ran the 1.6 code sample against 1.6.0 with TZ=Asia/Tokyo:

  • ExDate is 2005-04-03T22:00:00Z with DateTimeKind.Utc, and ToLocalTime() gives 2005-04-04T07:00:00+09:00.
  • DomainRenew given 2026-04-03T22:00:00.0Z sends curExpDate 2026-04-03.

The README is packed into the NuGet package, so nuget.org will show this guide from the next release.

🤖 Generated with Claude Code

Add sections for the 1.6.0 UTC dates change (affected properties, how
to display and compare the values, the DomainRenew fix) and the 1.4.1
TLS default (rebuild to pick it up), alongside the existing 1.5
certificate validation note.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ademar
ademar merged commit 0e9af46 into master Sep 25, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant