Repository navigation
[Release] 1.3.0: version, release notes and changelog - #91
Merged
Merged
Conversation
|
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.



Prepares the 1.3.0 release.
Why 1.3.0
The unreleased changes add features (problem details, retry policy, exception handler, compression, authentication, new host and client options), so a patch release is out. The public API compared with the
1.2.1tag has only additions, so code compiled against 1.2.1 keeps working. Several changes alter behaviour, but each makes an already-wrong setup fail earlier or tightens an edge case; they are marked in the changelog rather than treated as a major version.Changes
CHANGELOG.md:[Unreleased]becomes[1.3.0] - 2026-10-11, with a new empty[Unreleased]above it and updated compare links.CHANGELOG.md: [Fix] Answer only request-format violations with 400 (ArgusProtocolException) #63, [Fix] Percent-encode routes and validate header names and values #69, [Fix] Validate route templates at registration (#41) #73, [Fix] Negotiate the response serializer from the Accept header (#42) #75, [Feature] Return problem details from the host's built-in 400/406/503 responses (#53) #77 and [Feature] Validate the protocol version in request and status lines (#52) #81 now start with**Behavior change:**and say what changes. The [Fix] Negotiate the response serializer from the Accept header (#42) #75 line also records that a newArgusRequestno longer setsAccept: text/plain, which was not mentioned before.ArgusTransfer.csproj:Versionis 1.3.0 andPackageReleaseNotesis written from the changelog section. The README restructure ([Update] Restructure README into a landing page with a getting-started guide #61) and the file header corrections ([Fix] Correct stale file headers and Argus Health wording, add a header check (#58) #83) are left out of the package notes because they do not affect the package's behaviour.CITATION.cffis not changed here; the release workflow updates it.Verification
dotnet build ArgusTransfer.sln -warnaserror: 0 warnings, 0 errorsdotnet test ArgusTransfer.sln: 723 passeddotnet format ArgusTransfer.sln --verify-no-changes: no changesdotnet packproducesArgusTransfer.1.3.0.nupkgBefore releasing
If the release is cut on a later day, change the date in the changelog heading.
🤖 Generated with Claude Code