diff options
| author | Brandon Keiji <[email protected]> | 2025-04-25 00:52:24 +0000 |
|---|---|---|
| committer | GitHub <[email protected]> | 2025-04-25 00:52:24 +0000 |
| commit | a94a9ce3bf7bc015ebbd679d0d95be1c5d9762c2 (patch) | |
| tree | dd485e82e7968ba97a7d079f2fd0d8c959235454 | |
| parent | 7ea3dff49c367acbeddbea2184d6981b5b2c45bd (diff) | |
docs: update manual publishing section (#162)
| -rw-r--r-- | README.md | 10 |
1 files changed, 4 insertions, 6 deletions
@@ -84,20 +84,18 @@ The very first build of the container (with `npm run build` or `scripts/build_sa You can customize the sandbox in `Dockerfile` (e.g. for pre-installed utilities) or in `scripts/build_sandbox.sh` (e.g. for mounts `-v ...`, ports `-p ...`, or environment variables `-e ...`) and any changes should be automatically picked up by `npm run build` and `npm start` respectively. -## Publishing +## Manual Publish -Run the following commands: +We publish an artifact for each commit to our internal registry. But if you need to manually cut a local build, then run the following commands: ``` npm run clean npm install npm run auth -npm run stage -npm publish --tag=dogfood --workspaces +npm run prerelease:dev +npm publish --workspaces ``` -> TODO(b/412808531): add arguments to `npm run stage` to give us more control over the version number staged for publishing - ### Attaching from VSCode You can have VSCode (or forks) attach to a running sandbox using the [Dev Containers](https://marketplace.cursorapi.com/items?itemName=ms-vscode-remote.remote-containers) extension. Simply use `Dev Containers: Attach to Running Container ...` command and select your container named `gemini-code-sandbox-#`. Once attached you can open the project folder at `/sandbox/<project>`. You may need to set the VSCode setting `dev.containers.dockerPath` (e.g. to `podman`) if you are not using Docker, and otherwise you may be prompted by the extension to install Docker if missing from your system. |