feat: set dogfood artifact registry as the default publishing endpoint (#135)
This commit is contained in:
parent
7f3798e180
commit
4c951ea435
5
.npmrc
5
.npmrc
|
@ -1,3 +1,2 @@
|
||||||
; TODO(b/411429188): re-enable and migrate once our private GCP project is up
|
@gemini-code:registry=https://us-west1-npm.pkg.dev/gemini-code-dev/gemini-code/
|
||||||
; @gemini-code:registry=https://us-west1-npm.pkg.dev/gemini-code-dev/gemini-code/
|
//us-west1-npm.pkg.dev/gemini-code-dev/gemini-code/:always-auth=true
|
||||||
; //us-west1-npm.pkg.dev/gemini-code-dev/gemini-code/:always-auth=true
|
|
||||||
|
|
14
README.md
14
README.md
|
@ -84,6 +84,20 @@ 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.
|
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
|
||||||
|
|
||||||
|
Run the following commands:
|
||||||
|
|
||||||
|
```
|
||||||
|
npm run clean
|
||||||
|
npm install
|
||||||
|
npm run auth
|
||||||
|
npm run stage
|
||||||
|
npm publish --tag=dogfood --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
|
### 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.
|
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.
|
||||||
|
|
|
@ -6768,7 +6768,7 @@
|
||||||
},
|
},
|
||||||
"packages/cli": {
|
"packages/cli": {
|
||||||
"name": "@gemini-code/cli",
|
"name": "@gemini-code/cli",
|
||||||
"version": "0.1.0",
|
"version": "*",
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"@gemini-code/server": "*",
|
"@gemini-code/server": "*",
|
||||||
"@google/genai": "^0.8.0",
|
"@google/genai": "^0.8.0",
|
||||||
|
@ -6804,7 +6804,7 @@
|
||||||
},
|
},
|
||||||
"packages/server": {
|
"packages/server": {
|
||||||
"name": "@gemini-code/server",
|
"name": "@gemini-code/server",
|
||||||
"version": "0.1.0",
|
"version": "*",
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"@google/genai": "^0.8.0",
|
"@google/genai": "^0.8.0",
|
||||||
"diff": "^7.0.0",
|
"diff": "^7.0.0",
|
||||||
|
|
|
@ -17,7 +17,7 @@
|
||||||
"typecheck": "tsc --noEmit --jsx react",
|
"typecheck": "tsc --noEmit --jsx react",
|
||||||
"format": "prettier --write .",
|
"format": "prettier --write .",
|
||||||
"preflight": "npm run format --workspaces --if-present && npm run lint --workspaces --if-present && npm run test --workspaces --if-present",
|
"preflight": "npm run format --workspaces --if-present && npm run lint --workspaces --if-present && npm run test --workspaces --if-present",
|
||||||
"artifactregistry-login": "npx google-artifactregistry-auth",
|
"auth": "npx google-artifactregistry-auth",
|
||||||
"stage": "npm run stage:version --workspaces && npm run stage:deps --workspaces"
|
"stage": "npm run stage:version --workspaces && npm run stage:deps --workspaces"
|
||||||
},
|
},
|
||||||
"devDependencies": {
|
"devDependencies": {
|
||||||
|
|
|
@ -16,7 +16,8 @@
|
||||||
"format": "prettier --write .",
|
"format": "prettier --write .",
|
||||||
"test": "vitest run",
|
"test": "vitest run",
|
||||||
"stage:version": "node ../../scripts/bind_package_version.js",
|
"stage:version": "node ../../scripts/bind_package_version.js",
|
||||||
"stage:deps": "node ../../scripts/bind_package_dependencies.js"
|
"stage:deps": "node ../../scripts/bind_package_dependencies.js",
|
||||||
|
"prepack": "npm run build"
|
||||||
},
|
},
|
||||||
"files": [
|
"files": [
|
||||||
"dist"
|
"dist"
|
||||||
|
|
|
@ -12,7 +12,8 @@
|
||||||
"format": "prettier --write .",
|
"format": "prettier --write .",
|
||||||
"test": "vitest run",
|
"test": "vitest run",
|
||||||
"stage:version": "node ../../scripts/bind_package_version.js",
|
"stage:version": "node ../../scripts/bind_package_version.js",
|
||||||
"stage:deps": "node ../../scripts/bind_package_dependencies.js"
|
"stage:deps": "node ../../scripts/bind_package_dependencies.js",
|
||||||
|
"prepack": "npm run build"
|
||||||
},
|
},
|
||||||
"files": [
|
"files": [
|
||||||
"dist"
|
"dist"
|
||||||
|
|
Loading…
Reference in New Issue