You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
reactiveui/refit@053873c309b518d21aa128c246ff8c8b2e38bed4 feat(analyzers): explain why a method cannot generate and flag unbound route placeholders (#2340) @glennawatson
reactiveui/refit@d864935e7f389e76cae04aecc8c8991712f8d050 feat(testing): add controllable streams, request capture and a test clock to Refit.Testing (#2337) @glennawatson
reactiveui/refit@04187430b0a947b4d5d3280f3fd5ac6cfebe67c1 feat(bodies): typed JSON Lines uploads from IEnumerable and IAsyncEnumerable (#2338) @glennawatson
reactiveui/refit@7aa89fa16df2a8c69811a07d5fca14d4121b999a chore: remove the Jekyll site files now that GitHub Pages redirects to reactiveui.net @glennawatson
Refit 16.0.0 is a major version because the .NET 11 assemblies are built without runtime-async. The public API does not change.
Why runtime-async is off
In .NET 10 and older, the C# compiler adds a state machine to each async method. The state machine stores the local variables and tracks where to resume after each await.
.NET 11 adds a feature called runtime-async. The runtime does this work instead, so async code can run faster.
Refit 12.0.0 to 15.2.0 built the .NET 11 assemblies with runtime-async on. We did not use it with older .NET 8-10 nor .NET framework assemblies.
The feature needs a runtime that supports it. CoreCLR does, and Mono does not.
Blazor WebAssembly runs on Mono unless you opt into CoreCLR. WASI, Android API levels 21 to 23, and apps that set UseMonoRuntime=true also run on Mono.
Refit built with runtime-async can fail in every app that runs on Mono.
Microsoft builds its framework assemblies twice, once for each runtime. ASP.NET Core turns the feature on only for libraries inside the shared framework, and leaves it off for libraries that also ship on NuGet.
A NuGet package ships one build for every runtime, so Refit leaves the feature off. The feature is opt-in, so doing nothing is the correct setting.
Apps that target .NET 10 or older are not affected, because only the .NET 11 assemblies used the feature. Apps on .NET 11 that run on CoreCLR do not get the speed gain inside Refit's own async code.
You can turn on runtime-async in your own app if it runs only on CoreCLR.
Other changes
Refit has a documentation website at https://reactiveui.net/documentation/refit/. It has guides for requests, results, clients, serialization and testing, and one page that lists the full API.
The README is a short overview of the packages, the build requirements and the links to the website.
src/examples/Documentation has a project for every website page, plus larger samples for topics such as multipart uploads, serializers and compression. Each project builds with Refit.slnx and checks its results against local replies, so none needs a live service.
On older target frameworks, Refit checks the cancellation token before it buffers or reads HTTP content. A token that is already cancelled stops the operation before it starts.
Doc comments were corrected to match how Refit works. They state that [Options] sends OPTIONS, that [Url] accepts an empty path or /, and that [PathPrefix] does not add a leading slash. The Refit.Testing docs state that VerifyAllCalled ignores reusable and fallback routes.
The Blazor WebAssembly sample builds for .NET 10 and .NET 11. It uses a generated client and JSON source generation, and builds without trimmer warnings.
Refit depends on ReactiveUI.Primitives 8.0.0. On .NET 11, Refit.HttpClientFactory depends on Microsoft.Extensions.Http 11.0.0-rc.1, and other targets depend on 10.0.12.
SECURITY.md lists the supported versions and explains how to report a vulnerability through GitHub private reporting.
CI workflows drop code scanning of fork pull requests and pass sourceRef to the shared release workflow. Renovate handles package updates per target framework, and the generator snapshot tests use a small in-repo helper instead of the Verify packages.
🗞️ What's Changed
✨ Features
reactiveui/refit@6f0507fa061f1844a8da6ea92e839b622dfc74ef feat: expand generated request support & docs (#2329) @glennawatson
reactiveui/refit@053873c309b518d21aa128c246ff8c8b2e38bed4 feat(analyzers): explain why a method cannot generate and flag unbound route placeholders (#2340) @glennawatson
reactiveui/refit@d864935e7f389e76cae04aecc8c8991712f8d050 feat(testing): add controllable streams, request capture and a test clock to Refit.Testing (#2337) @glennawatson
reactiveui/refit@04187430b0a947b4d5d3280f3fd5ac6cfebe67c1 feat(bodies): typed JSON Lines uploads from IEnumerable and IAsyncEnumerable (#2338) @glennawatson
reactiveui/refit@7aa89fa16df2a8c69811a07d5fca14d4121b999a chore: remove the Jekyll site files now that GitHub Pages redirects to reactiveui.net @glennawatson
Refit 16.0.0 is a major version because the .NET 11 assemblies are built without runtime-async. The public API does not change.
Why runtime-async is off
In .NET 10 and older, the C# compiler adds a state machine to each async method. The state machine stores the local variables and tracks where to resume after each await.
.NET 11 adds a feature called runtime-async. The runtime does this work instead, so async code can run faster.
Refit 12.0.0 to 15.2.0 built the .NET 11 assemblies with runtime-async on. We did not use it with older .NET 8-10 nor .NET framework assemblies.
The feature needs a runtime that supports it. CoreCLR does, and Mono does not.
Blazor WebAssembly runs on Mono unless you opt into CoreCLR. WASI, Android API levels 21 to 23, and apps that set UseMonoRuntime=true also run on Mono.
Refit built with runtime-async can fail in every app that runs on Mono.
Microsoft builds its framework assemblies twice, once for each runtime. ASP.NET Core turns the feature on only for libraries inside the shared framework, and leaves it off for libraries that also ship on NuGet.
A NuGet package ships one build for every runtime, so Refit leaves the feature off. The feature is opt-in, so doing nothing is the correct setting.
Apps that target .NET 10 or older are not affected, because only the .NET 11 assemblies used the feature. Apps on .NET 11 that run on CoreCLR do not get the speed gain inside Refit's own async code.
You can turn on runtime-async in your own app if it runs only on CoreCLR.
Other changes
Refit has a documentation website at https://reactiveui.net/documentation/refit/. It has guides for requests, results, clients, serialization and testing, and one page that lists the full API.
The README is a short overview of the packages, the build requirements and the links to the website.
src/examples/Documentation has a project for every website page, plus larger samples for topics such as multipart uploads, serializers and compression. Each project builds with Refit.slnx and checks its results against local replies, so none needs a live service.
On older target frameworks, Refit checks the cancellation token before it buffers or reads HTTP content. A token that is already cancelled stops the operation before it starts.
Doc comments were corrected to match how Refit works. They state that [Options] sends OPTIONS, that [Url] accepts an empty path or /, and that [PathPrefix] does not add a leading slash. The Refit.Testing docs state that VerifyAllCalled ignores reusable and fallback routes.
The Blazor WebAssembly sample builds for .NET 10 and .NET 11. It uses a generated client and JSON source generation, and builds without trimmer warnings.
Refit depends on ReactiveUI.Primitives 8.0.0. On .NET 11, Refit.HttpClientFactory depends on Microsoft.Extensions.Http 11.0.0-rc.1, and other targets depend on 10.0.12.
SECURITY.md lists the supported versions and explains how to report a vulnerability through GitHub private reporting.
CI workflows drop code scanning of fork pull requests and pass sourceRef to the shared release workflow. Renovate handles package updates per target framework, and the generator snapshot tests use a small in-repo helper instead of the Verify packages.
🗞️ What's Changed
✨ Features
reactiveui/refit@6f0507fa061f1844a8da6ea92e839b622dfc74ef feat: expand generated request support & docs (#2329) @glennawatson
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)
AI Reviewer: run a review on demand. To trigger the first review automatically, go to your organization or repository integration settings. AI can make mistakes. Always validate suggestions.
TIP This summary will be updated as you push new changes.
Closing automatically: Refit and Refit.Newtonsoft.Json are already declared at the proposed version or above, so merging this would change nothing.
Raised by PanoramicData.NugetManagement's Dependabot triage. If this is wrong, reopen it — and the mistake is worth reporting, because triage only closes pull requests whose target version the repository already declares.
OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
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
dependenciesPull requests that update a dependency file.NETPull requests that update .NET code
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.
dependabot
Bot
added
.NET
Updated Refit from 15.2.0 to 16.3.0.
Release notes
Sourced from Refit's releases.
16.3.0
🗞️ What's Changed
✨ Features
🔗 Full Changelog: reactiveui/refit@v16.2.0...v16.3.0
🙌 Contributions
💖 Thanks to all the contributors: @glennawatson
16.2.0
🗞️ What's Changed
✨ Features
🧹 General Changes
✅ Tests
📝 Documentation
📦 Dependencies
🔗 Full Changelog: reactiveui/refit@v16.1.0...v16.2.0
🙌 Contributions
💖 Thanks to all the contributors: @glennawatson
🤖 Automated services that contributed: renovate[bot]
16.1.0
🗞️ What's Changed
✨ Features
📝 Documentation
📌 Other
🔗 Full Changelog: reactiveui/refit@v16.0.0...v16.1.0
🙌 Contributions
💖 Thanks to all the contributors: @glennawatson
16.0.0
Summary
Refit 16.0.0 is a major version because the .NET 11 assemblies are built without runtime-async. The public API does not change.
Why runtime-async is off
await.UseMonoRuntime=truealso run on Mono.Other changes
src/examples/Documentationhas a project for every website page, plus larger samples for topics such as multipart uploads, serializers and compression. Each project builds withRefit.slnxand checks its results against local replies, so none needs a live service.[Options]sendsOPTIONS, that[Url]accepts an empty path or/, and that[PathPrefix]does not add a leading slash. The Refit.Testing docs state thatVerifyAllCalledignores reusable and fallback routes.SECURITY.mdlists the supported versions and explains how to report a vulnerability through GitHub private reporting.sourceRefto the shared release workflow. Renovate handles package updates per target framework, and the generator snapshot tests use a small in-repo helper instead of the Verify packages.🗞️ What's Changed
✨ Features
🧹 General Changes
📝 Documentation
📦 Dependencies
... (truncated)
Commits viewable in compare view.
Updated Refit.Newtonsoft.Json from 15.2.0 to 16.3.0.
Release notes
Sourced from Refit.Newtonsoft.Json's releases.
16.3.0
🗞️ What's Changed
✨ Features
🔗 Full Changelog: reactiveui/refit@v16.2.0...v16.3.0
🙌 Contributions
💖 Thanks to all the contributors: @glennawatson
16.2.0
🗞️ What's Changed
✨ Features
🧹 General Changes
✅ Tests
📝 Documentation
📦 Dependencies
🔗 Full Changelog: reactiveui/refit@v16.1.0...v16.2.0
🙌 Contributions
💖 Thanks to all the contributors: @glennawatson
🤖 Automated services that contributed: renovate[bot]
16.1.0
🗞️ What's Changed
✨ Features
📝 Documentation
📌 Other
🔗 Full Changelog: reactiveui/refit@v16.0.0...v16.1.0
🙌 Contributions
💖 Thanks to all the contributors: @glennawatson
16.0.0
Summary
Refit 16.0.0 is a major version because the .NET 11 assemblies are built without runtime-async. The public API does not change.
Why runtime-async is off
await.UseMonoRuntime=truealso run on Mono.Other changes
src/examples/Documentationhas a project for every website page, plus larger samples for topics such as multipart uploads, serializers and compression. Each project builds withRefit.slnxand checks its results against local replies, so none needs a live service.[Options]sendsOPTIONS, that[Url]accepts an empty path or/, and that[PathPrefix]does not add a leading slash. The Refit.Testing docs state thatVerifyAllCalledignores reusable and fallback routes.SECURITY.mdlists the supported versions and explains how to report a vulnerability through GitHub private reporting.sourceRefto the shared release workflow. Renovate handles package updates per target framework, and the generator snapshot tests use a small in-repo helper instead of the Verify packages.🗞️ What's Changed
✨ Features
🧹 General Changes
📝 Documentation
📦 Dependencies
... (truncated)
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)