Bump Refit from 10.1.6 to 11.0.0

[dependabot]

Updated Refit from 10.1.6 to 11.0.0.

Release notes

Sourced from Refit's releases.

11.0.0

⚠️ This is a breaking release (major: 10.x → 11.0.0)

11.0.0 reworks Refit's error/exception model and tightens interface validation. Most apps will compile, but code that inspects ApiResponse.Error, reads StatusCode, or catches transport exceptions around Refit calls will need changes. These are the same breaking changes that briefly shipped in the now‑delisted 10.1.7 and were reported by the community in #​2114.

💡 Need a drop‑in, non‑breaking replacement for 10.1.6? Use 10.2.0 — it is 10.1.6 re‑signed with a valid certificate (the 10.1.6 cert was revoked, see #​2114). Move to 11.0.0 when you're ready to adopt the changes below.

💥 What changed & how to migrate

1. ApiResponse<T>.Error is now ApiExceptionBase? (was ApiException?) (#​2052)
A new abstract base ApiExceptionBase now sits under both ApiException and the new ApiRequestException. ApiExceptionBase does not expose Content / HasContent — those still live on ApiException.

// before
string? body = response.Error?.Content;

// after — narrow to ApiException first
if (response.Error is ApiException apiEx)
{
    string? body = apiEx.Content;   // Content/HasContent are on ApiException
}

2. New ApiRequestException wraps transport/connection failures (#​2052)
Exceptions thrown by HttpClient.SendAsync before a response arrives — HttpRequestException (DNS/host unreachable), TaskCanceledException (timeouts), etc. — are now wrapped in ApiRequestException : ApiExceptionBase, carrying the full request context. For ApiResponse<T> return types these are now surfaced via .Error instead of only being thrown, so you no longer need a separate try/catch and IsSuccessful check.

// catching transport errors: catch the base (or ApiRequestException) now
catch (ApiExceptionBase ex) { /* covers ApiException + ApiRequestException */ }

3. ApiResponse<T>.StatusCode is now nullable (HttpStatusCode?) (#​2052)
When the request never reached the server there is no status code. Code that assumed a non‑null value must handle null:

int code = (int)response.StatusCode;          // ❌ won't compile / may throw
int? code = (int?)response.StatusCode;         // ✅ handle the no-response case

4. Stricter interface validation + enum name handling (#​2068)
Synchronous return types are now only permitted for generated/non‑public interface members (RestMethodInfo enforces the rule), and the System.Text.Json enum converter now maps serialized names both ways (including JsonStringEnumMemberName on .NET 9+). Interfaces that previously relied on unsupported sync members may now fail generation.

---

🗞️ What's Changed

✨ Features & Enhancements

• Create ApiRequestException for wrapping SendAsync exceptions (new error model) by @​PressXtoChris in #​2052
• Support sync interface members & enum names by @​ChrisPulman in #​2068
• Add AddRefitClient overloads and tests by @​ChrisPulman in #​2084

... (truncated)

10.2.0

NOTE

This is a re-release of v10.1.6 which had a certificate revoked.

🗞️ What's Changed

🐛 Fixes

• reactiveui/refit@​cfe6862f468ce793fd5d5557ff47554de800a198 Fixes examples, issues 2058, 1761, 1889, and 2056 (#​2061) @​ChrisPulman
• reactiveui/refit@​71e7a32b8c0fd428ae29949b45bf13f4d17bc2b7 Fix is packable (#​2063) @​ChrisPulman

🧹 General Changes

• reactiveui/refit@​c945712afe664c07babcb1193e9f68ec20e48eb4 Update AoT, Add Roslyn 5.0, Update serialisation (#​2062) @​ChrisPulman

📦 Dependencies

• reactiveui/refit@​d3b9f6eb2242728b1577489781d9b1ac9e41ceaf chore(deps): update .net test stack (#​2054) @​ChrisPulman @​renovate[bot]
• reactiveui/refit@​804eb41f61b200c02765c7a0b63f4ddfe9164528 chore(deps): update .net test stack to v8 (#​2057) @​renovate[bot]

📌 Other

• reactiveui/refit@​14811e0b27178a9b3da3b5d4bdda1e9cd8ea33fd Enhance release workflow with new jobs and permissions @​ChrisPulman
• reactiveui/refit@​49858e348e9444b82735068c15919c3f31942bf4 Bump version from 10.0 to 10.1 @​ChrisPulman
• reactiveui/refit@​2f43b67c0a78b76c048931dede5f671625b807a0 Remove productNamespacePrefix from release workflow @​ChrisPulman

🔗 Full Changelog: reactiveui/refit@10.0.1...10.1.6

🙌 Contributions

💖 Thanks to all the contributors: @​ChrisPulman

🤖 Automated services that contributed: @​renovate[bot]

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #32.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

While this PR initiates the upgrade to Refit 11.0.0, it is currently incomplete and will likely cause build or runtime failures. The primary issue is a version mismatch: the core Refit library was updated to v11, but the Refit.HttpClientFactory package remains on v10. These packages are tightly coupled and must be updated together to avoid assembly binding issues.

Furthermore, Refit 11 introduces breaking changes to the ApiResponse model, including changing the Error property type to ApiExceptionBase and making StatusCode nullable. Since this PR only modifies Directory.Packages.props, any application code consuming these properties will require manual updates to remain compatible. It is recommended to address the companion package version and the resulting code breakages before merging.

About this PR

• This major version bump introduces breaking changes to the Refit error model and status code handling. As the current diff only includes the package version update in Directory.Packages.props, the application code likely needs adjustments to handle ApiExceptionBase and nullable HttpStatusCode values to avoid compilation or logic errors.

Test suggestions

• Verify application compilation against Refit 11.0.0 breaking changes
• Test ApiResponse error handling with the new ApiExceptionBase type
• Test logic involving ApiResponse.StatusCode to ensure it handles null (transport failures)
• Verify dependency compatibility between Refit 11.0.0 and Refit.HttpClientFactory 11.0.0

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify application compilation against Refit 11.0.0 breaking changes
2. Test ApiResponse error handling with the new ApiExceptionBase type
3. Test logic involving ApiResponse.StatusCode to ensure it handles null (transport failures)
4. Verify dependency compatibility between Refit 11.0.0 and Refit.HttpClientFactory 11.0.0

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}

[codacy-production]

_{🔴 HIGH RISK}

The Refit.HttpClientFactory package version (10.1.6) is now out of sync with the core Refit package (11.0.0). These libraries are tightly coupled and versioned together; mixing major versions typically leads to runtime assembly binding errors or NuGet dependency resolution failures. Update Refit.HttpClientFactory to 11.0.0.

Suggested change

	<PackageVersion Include="Refit" Version="11.0.0" />
	<PackageVersion Include="Refit.HttpClientFactory" Version="10.1.6" />
	<PackageVersion Include="Refit.HttpClientFactory" Version="11.0.0" />