Skip to content

docs: update readme to reflect devnet 4 status#286

Open
MegaRedHand wants to merge 1 commit intodevnet4from
devnet4-update-readme
Open

docs: update readme to reflect devnet 4 status#286
MegaRedHand wants to merge 1 commit intodevnet4from
devnet4-update-readme

Conversation

@MegaRedHand
Copy link
Copy Markdown
Collaborator

No description provided.

@github-actions
Copy link
Copy Markdown

🤖 Kimi Code Review

This PR contains documentation-only changes to README.md reflecting the devnet version progression (3→4, 4→5). No consensus-critical code is modified.

Review:

The changes are straightforward and consistent:

  1. Lines 100, 107-111, 125: Correctly updates version references from devnet3/devnet4 to devnet4/devnet5, matching the stated policy that "Support for older devnet releases is discontinued when the next devnet version is released."

  2. Line 111: The link to issue Add support for pq-devnet-5 #285 for pq-devnet-5 tracking is appropriate for a work-in-progress feature.

  3. No issues found: All Docker tag references, section headers, and feature list items remain internally consistent.

Approval: LGTM. This is a standard version-bump documentation update with no security or correctness implications.


Automated review by Kimi (Moonshot AI) · kimi-k2.5 · custom prompt

@github-actions
Copy link
Copy Markdown

🤖 Claude Code Review

PR #286docs: update readme to reflect devnet 4 status

Author: MegaRedHand (Tomás Grüner)
Type: Documentation-only change
Size: 6 additions, 6 deletions


Overview

This PR updates README.md to reflect that pq-devnet-4 is now the active running devnet and pq-devnet-5 is the next target. It also updates the roadmap link from issue #155 (devnet-4) to issue #285 (devnet-5).


Analysis

Correctness

All changes are internally consistent:

One potential concern: The pq-devnet-3 section is now silently dropped — it was the "currently running" devnet in the previous version, and after this PR it disappears from the named sections entirely. This is presumably intentional (it falls under "Older devnets"), but it's worth confirming the "Older devnets" prose below correctly captures that devnet-3 is discontinued.

Link quality

The new pq-devnet-5 section drops the direct spec link (previously there was a link to the leanEthereum/pm breakout-rooms doc). Instead it links to the tracking issue (#285). This is a minor downgrade in discoverability if an external spec document exists. If a pq-devnet-5 spec doc is already published, it would be better to link it directly (or in addition to the issue).

The pq-devnet-4 section similarly drops its spec link, replacing it with prose-only. If the spec doc at leanEthereum/pm is still accessible and correct, restoring the link would be helpful for contributors referencing the spec.

No issues with:

  • Formatting or markdown structure
  • Consistency between sections
  • Accuracy of Docker tag naming

Verdict

Straightforward, low-risk documentation update. The changes are accurate and internally consistent. Two minor suggestions worth considering before merging:

  1. Confirm "Older devnets" prose adequately covers devnet-3 discontinuation, since the named section is removed.
  2. Consider re-adding direct links to the pq-devnet-4 and pq-devnet-5 spec documents if/when they are published, to maintain the same discoverability that the devnet-3 section had.

Approved with minor notes. No code changes, no correctness or security concerns.


Automated review by Claude (Anthropic) · sonnet · custom prompt

@github-actions
Copy link
Copy Markdown

🤖 Codex Code Review

No findings.

This PR is documentation-only: the diff updates devnet/release text in README.md, README.md, and README.md. It does not touch Rust code, consensus logic, networking, SSZ, signatures, or state-transition paths, so I found no correctness, security, performance, or memory-safety issues to call out.

Residual risk is limited to documentation accuracy. No code testing is applicable for this diff.


Automated review by OpenAI Codex · gpt-5.4 · custom prompt

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Apr 14, 2026

Greptile Summary

Documentation update bumping the README from devnet 3 to devnet 4 as the current running devnet. The pq-devnet-4 section is updated to reflect active status, pq-devnet-5 is introduced as the next target (linked to issue #285), and the roadmap entry is updated accordingly.

Confidence Score: 5/5

Documentation-only change, safe to merge.

All changes are minor documentation updates with no code impact. No P0/P1 findings were identified.

No files require special attention.

Important Files Changed

Filename Overview
README.md Promotes pq-devnet-4 from "in progress" to current, adds pq-devnet-5 as next target, and updates roadmap issue link from #155 to #285.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
    D1[devnet1] --> D2[devnet2]
    D2 --> D3[devnet3]
    D3 --> D4["devnet4 ✅ current"]
    D4 --> D5["devnet5 🔜 in progress"]

    style D4 fill:#2d6a4f,color:#fff
    style D5 fill:#457b9d,color:#fff
    style D1 fill:#555,color:#fff
    style D2 fill:#555,color:#fff
    style D3 fill:#555,color:#fff
Loading

Reviews (1): Last reviewed commit: "docs: update readme to reflect devnet 4 ..." | Re-trigger Greptile

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.

1 participant