@multiplayer-app/sandbox 3.0.0-wip-yjs-state-changes.0 → 4.0.0-wip-yjs-state-changes.0

package/README.md

@@ -114,12 +114,15 @@ Architecture-specific tags use `<version>-<arch>` so a separate publishing
 workflow can push them and optionally create a multi-architecture `<version>`
 manifest. The build script never uploads files or pushes images.
 
-Tags matching `sandbox-v*` run three release jobs: npm package publication and
-the two architecture-specific base-image publishers start after lint in
-parallel; once both architectures are available, a final job creates the
-multi-architecture Docker tags. The publisher expects the repository variable
-`SANDBOX_BASE_IMAGES_S3_BUCKET`, the existing `DOCKERHUB_ORGANIZATION` variable,
-and the existing `AWS_ROLE_ARN` and `DOCKERHUB_OIDC_ID` secrets.
+Tags matching `sandbox-v*` run npm package publication alongside base-image
+publishers for every combination of `test`, `staging`, `production`, and `demo`
+with `x86_64` and `aarch64`; these jobs publish only QEMU, Firecracker, and
+Lambda artifacts to each environment's S3 bucket. Each S3 publisher enters its
+GitHub environment and expects `ARTIFACTS_S3_BUCKET` plus `AWS_ROLE_ARN` there.
+Container images are published globally exactly once per architecture by a
+separate job, followed by one global multi-architecture manifest job. Those jobs
+use the repository-level `DOCKERHUB_ORGANIZATION` variable and
+`DOCKERHUB_OIDC_ID` secret and do not enter a GitHub environment.
 
 The runner-specific paths intentionally duplicate shared artifacts. That keeps
 each S3 prefix self-contained and allows runner formats to evolve independently.

package/dist/cli.js

@@ -28,7 +28,7 @@ var import_config5 = require("dotenv/config");
 var import_commander = require("commander");
 
 // package.json
-var version = "3.0.0-wip-yjs-state-changes.0";
+var version = "4.0.0-wip-yjs-state-changes.0";
 
 // src/config.ts
 var import_os2 = __toESM(require("os"));