diff options
Diffstat (limited to 'docs/deployment.md')
| -rw-r--r-- | docs/deployment.md | 10 |
1 files changed, 4 insertions, 6 deletions
diff --git a/docs/deployment.md b/docs/deployment.md index 1ad872c0..12ea0655 100644 --- a/docs/deployment.md +++ b/docs/deployment.md @@ -103,14 +103,12 @@ There are two distinct build processes used, depending on the distribution chann **Docker sandbox image** -The Docker-based execution method is supported by the `gemini-cli-sandbox` container image. This image is published to a container registry and contains a pre-installed, global version of Gemini CLI. The `scripts/prepare-cli-packagejson.js` script dynamically injects the URI of this image into the CLI's `package.json` before publishing, so the CLI knows which image to pull when the `--sandbox` flag is used. +The Docker-based execution method is supported by the `gemini-cli-sandbox` container image. This image is published to a container registry and contains a pre-installed, global version of Gemini CLI. ## Release process -A unified script, `npm run publish:release`, orchestrates the release process. The script performs the following actions: +The release process is automated through GitHub Actions. The release workflow performs the following actions: 1. Build the NPM packages using `tsc`. -2. Update the CLI's `package.json` with the Docker image URI. -3. Build and tag the `gemini-cli-sandbox` Docker image. -4. Push the Docker image to the container registry. -5. Publish the NPM packages to the artifact registry. +2. Publish the NPM packages to the artifact registry. +3. Create GitHub releases with bundled assets. |