release: 1.0.0

[StuartMeeks]

Stacked on #30 (which is stacked on #29) — retargets automatically as those merge. Merge order: #29 → #30 → this.

First stable release. The public surface becomes a SemVer commitment: changing it afterwards requires a 2.0.0.

Breaking — for implementers only

IUpdateSource, IUpdateChecker and ISelfUpdater each carried an overload pair in which the abstract member was the one without the prerelease override, and the override-carrying member was a default interface implementation that discarded its argument:

// before 1.0.0
Task<RemoteRelease?> GetLatestAsync(string? channel, CancellationToken ct);           // abstract
Task<RemoteRelease?> GetLatestAsync(string? channel, bool? ovr, CancellationToken ct) // default
    => GetLatestAsync(channel, ct);                                                   // ...drops ovr

A custom IUpdateSource implementing the abstract member — the only one it was obliged to implement — compiled cleanly, ran, and silently ignored update --prerelease.

Now inverted: the override-carrying method is abstract, the no-override overload is the default and passes null. There is nothing left for an implementation to drop the override in.

Interface	Now abstract	Now the default overload
IUpdateSource	GetLatestAsync(string?, bool?, CancellationToken)	GetLatestAsync(string?, CancellationToken)
IUpdateChecker	CheckAsync(bool?, CancellationToken)	CheckAsync(CancellationToken)
ISelfUpdater	GetLatestReleaseAsync(bool?, CancellationToken)	GetLatestReleaseAsync(CancellationToken)

Callers are unaffected. Both overloads still exist with identical signatures, so every existing call site compiles and binds exactly as before. Only code that implements one of the three interfaces has to change, and the change is adding the bool? includePrereleasesOverride parameter to the method it already has and honouring it.

Package validation does not flag this, and that is expected rather than a gap: the API shape is unchanged — only which member carries the body moved, which an API-surface comparison cannot see. It passes against the 0.3.1 baseline. The break is a source and runtime break for implementers, which is why it is called out this prominently in the changelog rather than left to PKV.

Also in this PR

• HttpManifestSource flipped so its real logic sits on the override-carrying method. It still ignores the override — correct for a single-release manifest, and now documented on the method itself rather than on the delegating stub.
• InterfaceDefaultsTests implements each interface with only its abstract member and asserts the override arrives. If the abstract member ever moves back, the test project stops compiling.
• README's custom-source example carries the new signature.
• PackageValidationBaselineVersion 0.3.0 → 0.3.1. It was stale — 0.3.1 shipped to nuget.org on 2026-08-19.
• CHANGELOG [Unreleased] cut to [1.0.0] — 2026-08-21, with the Unreleased/1.0.0 compare and tag link refs added.

Verification

Release build: 0 warnings, 0 errors. dotnet test --configuration Release: 408 passed, 0 failed (204 × net8.0/net10.0), up from 392 with the new regression tests.

Package inspected: 1.0.0, lib/net8.0 + lib/net10.0, per-TFM floors intact (net8 8.0.2/8.0.1, net10 10.0.11), license expression, icon, readme and repository metadata all present.

No tag has been pushed. Publishing is tag-gated; tag v1.0.0 only after this merges.

🤖 Generated with Claude Code