-
Notifications
You must be signed in to change notification settings - Fork 189
chore: release v0.25 #1566
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: release v0.25 #1566
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
A release pull request updating the project with version v0.25.0, including breaking changes in the RpcServiceT trait to support both client- and server-side operations and multiple dependency bumps.
- Bumps version numbers in Cargo.toml and updates internal dependencies.
- Updates CHANGELOG.md to document new features, fixes, and breaking changes.
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
File | Description |
---|---|
Cargo.toml | Updated version and dependency versions to v0.25.0 |
CHANGELOG.md | Added detailed release notes including new features and fixes |
Co-authored-by: Copilot <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
Merge and release quickly |
Co-authored-by: James Wilson <[email protected]>
The reason for this change is to make it work for the client-side as well as make it easier to
with return
impl Future
instead require an associated type for theFuture
which in many casesrequires BoxFuture or ResponseFuture which improves ergonomics.
The downside of this change is that one has to duplicate the logic in the
batch
andcall
method to achieve the samefunctionality as before. Thus,
call
ornotification
is not being invoked in thebatch
method and one has to implementdoes separately.
For example now it's possible to write middleware that counts the number of method calls as follows (both client and server):
In addition because this middleware is quite powerful it's possible to
modify requests and specifically the request ID which should be avoided
because it may break the response verification especially for the client-side.
See #1565 for further information.
There are also a couple of other changes see the detailed changelog below.
[Added]
request timeout
getter (#1533)ServerConfigBuilder::build
(#1484)[Fixed]
http request body
log (#1540)[Changed]
Box<RawValue>
(#1545)ServerConfigBuilder/ServerConfig
replacesServerBuilder
duplicate setter methods (#1487)ProxyGetRequestLayer
http middleware support multiple path-method pairs (#1492)