feat(rpc): add package version to RPC response headers#21526
Merged
spalladino merged 1 commit intomerge-train/spartanfrom Mar 13, 2026
Merged
feat(rpc): add package version to RPC response headers#21526spalladino merged 1 commit intomerge-train/spartanfrom
spalladino merged 1 commit intomerge-train/spartanfrom
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Maddiaa0
approved these changes
Mar 13, 2026
Maddiaa0
reviewed
Mar 13, 2026
Member
Maddiaa0
left a comment
Maddiaa0
left a comment
There was a problem hiding this comment.
lgtm (missing a test though)
AztecBot
pushed a commit
that referenced
this pull request
Mar 13, 2026
## Motivation
The JSON-RPC server already returns `x-aztec-*` headers for protocol
component versions (chain id, rollup address, etc.), but does not
include the node's package version. This makes it harder to identify
which software version a node is running when debugging or monitoring.
## Approach
Extended `getVersioningMiddleware` to accept an optional
`packageVersion` parameter and emit it as an `x-aztec-packageVersion`
response header alongside existing versioning headers.
## Example
```
$ curl -s -D- http://localhost:8090 -H 'content-type: application/json' -d '[{"jsonrpc":"2.0","id":1,"method":"node_getNodeVersion","params":[]}]'
HTTP/1.1 200 OK
Vary: Accept-Encoding, Origin
Access-Control-Allow-Origin: *
Content-Type: application/json; charset=utf-8
x-aztec-l2CircuitsVkTreeRoot: 0x06624799e2080c43aba671cdece34d5f4cdff2122bc6be41d80bd903ca0975cc
x-aztec-l2ProtocolContractsHash: 0x23c2022f0b69b29e354b4f7612d5db3ba0bc4259d71ac9186ed272945a644b9c
x-aztec-packageVersion: 5.0.0
Content-Length: 43
Date: Fri, 13 Mar 2026 16:04:31 GMT
Connection: keep-alive
Keep-Alive: timeout=5
[{"jsonrpc":"2.0","id":1,"result":"5.0.0"}]
```
## Changes
- **stdlib**: Updated `getVersioningMiddleware` to accept an optional
`opts` bag with `packageVersion`, setting `x-aztec-packageVersion`
header when provided
- **aztec**: Wired `getPackageVersion()` into both the main and admin
RPC server middleware calls
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Collaborator
|
✅ Successfully backported to backport-to-v4-staging #21477. |
AztecBot
added a commit
that referenced
this pull request
Mar 14, 2026
BEGIN_COMMIT_OVERRIDE fix: orchestrator enqueue yield (#21286) chore: default multiplier (#21482) chore: update yarn.lock (#21479) chore: backport #21231 feat!: improve L2ToL1MessageWitness API to v4 (#21463) feat(rpc): add package version to RPC response headers (#21526) feat(ethereum): check VK tree root and protocol contracts hash in rollup compatibility (#21537) feat: add public log filtering by tag (#21561) END_COMMIT_OVERRIDE
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
3 participants
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.
Motivation
The JSON-RPC server already returns
x-aztec-*headers for protocol component versions (chain id, rollup address, etc.), but does not include the node's package version. This makes it harder to identify which software version a node is running when debugging or monitoring.Approach
Extended
getVersioningMiddlewareto accept an optionalpackageVersionparameter and emit it as anx-aztec-packageVersionresponse header alongside existing versioning headers.Example
Changes
getVersioningMiddlewareto accept an optionaloptsbag withpackageVersion, settingx-aztec-packageVersionheader when providedgetPackageVersion()into both the main and admin RPC server middleware calls