Skip to content

Conversation

@bobbinth
Copy link
Contributor

@bobbinth bobbinth commented Nov 9, 2025

This is a tracking PR for v0.13.0 release.

bobbinth and others added 3 commits November 15, 2025 20:36
- Normalized response size limits to 4MB
- Standardized naming in protobuf schema
This fixes an issue with the gRPC client builder where the content negotiation header
was only set if the RPC version was specified. This meant that if the version was unset
but the genesis commitment was set, that no header was written and the genesis
commitment was ignored.
…ethods (#1298)

Write RPC requests are now required to contain the network's genesis commitment
as part of their ACCEPT header.
* chore: unify and revisit query limits

* review: remove TooMany* error variants

* review: update limiter doc & rename MAX_RESPONSE_PAYLOAD_BYTES

* review: fix changelog entry

* review: create GENERAL_REQUEST_LIMIT const
* feat: track ntx latency

* review: fix changelog entries

* review: reduce lock risk & improve docs

* review: remove pending_latency field
* feat: add explorer to network monitor

* review: add warning for tips mismatch

* review: make graphql variable a constant

* review: move env example to devnet

* review: explicit frontend check in frontend

* review: abstract copy button & improve tip diff messagE

* review: create explorer.rs, improve code readability

* fix: remove duplicated changelog entry
* fix: reduce notes limits to 100

* review: fix comment padding

Co-authored-by: igamigo <ignacio.amigo@lambdaclass.com>

* review: move size comment to struct doc

* review: add size related comment to struct docs

---------

Co-authored-by: igamigo <ignacio.amigo@lambdaclass.com>
@Mirko-von-Leipzig
Copy link
Collaborator

The CI failures are kind of weird:

1. They don't happen locally.

2. They seem to refer to code that doesn't exist.

Its because this PR is a merge from next into main. So the code that is running and failing is the result of an auto-merge gone wrong.

If you're seeing different results locally, I suspect its due to our .gitattributes which says to use a better merge algorithm. Unfortunately, github does not implement this, so locally you get the better algo and the merge works better and everything is green. Then github shits the bed :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.