From b577e3e28a489ed4f415ee5296190f130218b226 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tom=C3=A1s=20Gr=C3=BCner?=
 <47506558+MegaRedHand@users.noreply.github.com>
Date: Mon, 6 Jul 2026 11:31:32 -0300
Subject: [PATCH 1/2] docs: clarify image tag descriptions

Clarify that unstable is built from the latest main commit and that
latest/devnetX are the latest *stable* devnet images (README, RELEASE).
Bump the stale devnet3 'at the time of writing' and docker pull examples
to devnet5, the current devnet.
---
 README.md  | 4 ++--
 RELEASE.md | 8 ++++----
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index 81001093..f0150479 100644
--- a/README.md
+++ b/README.md
@@ -114,8 +114,8 @@ Docker images are published to `ghcr.io/lambdaclass/ethlambda` with the followin
 | Tag | Description |
 |-----|-------------|
 | `devnetX` | Stable image for a specific devnet (e.g. `devnet4`) |
-| `latest` | Alias for the stable image of the currently running devnet |
-| `unstable` | Development builds; promoted to `devnetX`/`latest` once tested |
+| `latest` | Alias for the latest stable image of the currently running devnet |
+| `unstable` | Built from the latest main commit; promoted to `devnetX`/`latest` once tested |
 | `sha-XXXXXXX` | Specific commit |
 
 [`RELEASE.md`](./RELEASE.md) has more details on our release process and how to tag new images.
diff --git a/RELEASE.md b/RELEASE.md
index 185961a9..8a8126f6 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -21,9 +21,9 @@ exact commit it was built from.
 On top of that, the workflow accepts a comma-separated list of custom tags as a
 parameter (e.g. `latest,devnet2`). We use the following tagging convention:
 
-- `unstable` - the latest image built from the `main` branch, without any devnet-specific features
-- `latest` - the latest image built for the current devnet (`devnet3` at the time of writing)
-- `devnetX` - the latest image built with `devnetX` support (e.g. `devnet3`, `devnet4`)
+- `unstable` - the latest image built from the `main` branch
+- `latest` - the latest stable image built for the current devnet (`devnet5` at the time of writing)
+- `devnetX` - the latest stable image built with `devnetX` support (e.g. `devnet3`, `devnet4`)
 
 Future devnets will introduce new tags, with previous ones left without updates.
 
@@ -31,7 +31,7 @@ Future devnets will introduce new tags, with previous ones left without updates.
 
 ```bash
 docker pull ghcr.io/lambdaclass/ethlambda:unstable       # latest from main
-docker pull ghcr.io/lambdaclass/ethlambda:devnet3        # devnet3-compatible
+docker pull ghcr.io/lambdaclass/ethlambda:devnet5        # devnet5-compatible
 docker pull ghcr.io/lambdaclass/ethlambda:sha-12f8377    # pinned to a specific commit
 ```
 

From 4663527b36dd0d649e23c0a971c2a19e39c7e698 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tom=C3=A1s=20Gr=C3=BCner?=
 <47506558+MegaRedHand@users.noreply.github.com>
Date: Mon, 6 Jul 2026 12:52:04 -0300
Subject: [PATCH 2/2] docs: align devnetX examples with current devnet5

Greptile flagged the inline devnetX examples still listed devnet3/devnet4
while the docker-pull example was bumped to devnet5.
---
 RELEASE.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/RELEASE.md b/RELEASE.md
index 8a8126f6..ffd0add4 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -23,7 +23,7 @@ parameter (e.g. `latest,devnet2`). We use the following tagging convention:
 
 - `unstable` - the latest image built from the `main` branch
 - `latest` - the latest stable image built for the current devnet (`devnet5` at the time of writing)
-- `devnetX` - the latest stable image built with `devnetX` support (e.g. `devnet3`, `devnet4`)
+- `devnetX` - the latest stable image built with `devnetX` support (e.g. `devnet4`, `devnet5`)
 
 Future devnets will introduce new tags, with previous ones left without updates.