Skip to content

Conversation

@shariqnaiyer
Copy link
Collaborator

πŸ—’οΈ Description

Following the discussion in #309, I believe versioning the API endpoints from the get go is beneficial long term.

πŸ”— Related Issues or PRs

#309
#309 (comment)

βœ… Checklist

  • Ran tox checks to avoid unnecessary CI fails:
    uvx tox
  • Considered adding appropriate tests for the changes.

Copy link
Contributor

@ch4r10t33r ch4r10t33r left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

@shariqnaiyer
Copy link
Collaborator Author

I have versioned /health as well to be consistent with Beacon-API

Copy link
Contributor

@KolbyML KolbyML left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit: looks good

@KolbyML KolbyML merged commit 690298d into leanEthereum:main Jan 24, 2026
10 checks passed
@unnawut unnawut added the specs Scope: Changes to the specifications label Jan 24, 2026
@unnawut unnawut added this to the pq-devnet-2 milestone Jan 24, 2026
MegaRedHand added a commit to lambdaclass/ethlambda that referenced this pull request Jan 26, 2026
* fix: follow spec in /metrics and /health responses

See https://github.com/leanEthereum/leanSpec/blob/914e09333578072c6bf02d2d405f8c13d5b55d38/src/lean_spec/subspecs/api/server.py#L36-L46

* refactor: add new routes with dummy functions

* feat: use new endpoints with versioning and consistent naming

See:
- leanEthereum/leanSpec#323
- leanEthereum/leanSpec#325

* feat: implement the new routes

* fix: make it compile with new Store
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

specs Scope: Changes to the specifications

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants