chore(release): give embed its own release line

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
GitOrigin-RevId: f9d826ea1a2675ebf8f9b29fe530b39702748060

Author: 2 people

docs/RELEASING.md

@@ -29,12 +29,14 @@ Two identities:
    the patch. The timestamp sits in the patch slot, so these tags sort
    above every `MAJOR.MINOR.x` release — pin exact tags, not "highest".
 2. Conventional commits (`feat:`, `fix:`) accumulate into a release PR.
-   api, client-proxy, clickhouse-migrator, dashboard-api, embed,
+   api, client-proxy, clickhouse-migrator, dashboard-api,
    nomad-nodepool-apm and orchestrator share one coordinated SemVer with
    the rest of the platform: merging that PR tags each of them
-   `<component>-vX.Y.Z` at the same number, with changelog. envd is
-   versioned on its own and has its own release PR. (The same commits
-   arrive here through the copybara export.)
+   `<component>-vX.Y.Z` at the same number, with changelog. embed has
+   its own release PR, opened once the platform release is tagged, at
+   that same number. envd is versioned on its own and has its own
+   release PR. (The same commits arrive here through the copybara
+   export.)
 3. Either tag is a git tag only — no GitHub Release. The tag push
    publishes to `e2b-artifacts` — images as `:v<version>`, binaries as
    versioned objects in the public `e2b-artifact-binaries` bucket at

embed/README.md

@@ -56,8 +56,8 @@ deployment see [e2b.dev/enterprise](https://e2b.dev/enterprise).
   each one. Those reach the sandbox through the header routing above, at
   the address in `E2B_DASHBOARD_HOST` (default `localhost`); set it when a
   browser on another machine opens the dashboard without a tunnel.
-- **One version everywhere.** Embed is released with the platform at one
-  version, and that release moves every platform pin in
+- **One version everywhere.** Embed is released at the platform version once
+  that release is tagged, and that release moves every platform pin in
   [`compose/.env`](compose/.env) and the kustomization. To pin an install, pin
   the commit: put it in place of `main` in the raw URLs, or add
   `?ref=<commit>` to the git URLs.

embed/compose/.env

@@ -1,6 +1,5 @@
-# Platform pins. api, db-migrator, dashboard-api, client-proxy, clickhouse-migrator,
-# the orchestrator and the three stack images below are released together with
-# Embed at one version, and each release moves these lines to it: the trailing
+# Platform pins. Embed is released at the platform version once that release
+# is tagged, and each Embed release moves these lines to it: the trailing
 # marker is what the release tooling rewrites. Everything without a marker is
 # pinned by hand.
 E2B_API_IMAGE=us-docker.pkg.dev/e2b-artifacts/api/api:v0.14.202609170000-908833e4c12 # x-release-please-version

embed/docs/REFERENCE.md

@@ -111,8 +111,8 @@ pins in [`kubernetes/kustomization.yaml`](../kubernetes/kustomization.yaml).
 The 3 stack images live in the `embed` repository of the `e2b-artifacts`
 registry.
 
-Embed is released together with the platform at one version. That release
-moves every platform pin in both files to it: api, db-migrator,
+Embed is released at the platform version once that release is tagged.
+That release moves every platform pin in both files to it: api, db-migrator,
 dashboard-api, client-proxy, clickhouse-migrator, the orchestrator and the 3
 stack images, the lines carrying a release marker. A checkout at a release
 therefore names one version everywhere and pulls exactly what that release