changelog: daily entries through 2026-09-06 - #1485
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces the release notes for September 6, 2026, highlighting key features like internal npm registry support and various fixes across GCP Secret Manager, cold-start role bindings, and Azure DevOps clone URLs. The reviewer feedback recommends minor copy-editing improvements, specifically correcting a typo and rephrasing a grammatically awkward sentence to enhance the readability of the changelog.
| * **Internal npm registry for image builds (#1476):** `NPM_REGISTRY` build arg and `NPM_CONFIG_FILE` BuildKit secret enable image builds behind corporate proxies where registry.npmjs.org is blocked. Backward-compatible — defaults to public registry. | ||
|
|
||
| ## 🐛 Fixes | ||
| * **GCP Secret Manager NotFound mapping (#1478):** gRPC `NotFound` in `GCPBackend.Get()` was wrapped as a generic error instead of `store.ErrNotFound`, breaking `MigratePluginSecrets` which skips migration on unexpected errors — caused Discord down ~15h on scion-sagan. |
There was a problem hiding this comment.
The phrase "caused Discord down ~15h" is grammatically awkward. Consider rephrasing it to "caused ~15h of Discord downtime" or "caused Discord to be down for ~15h" for better readability.
| * **`as_needed` secret keys for broker autodetect (#1483):** Hub-level `as_needed` secrets (e.g. `GEMINI_API_KEY`) were invisible to the broker autodetect when the harness default_type didn't require them. Hub now passes `AvailableAsNeededKeys` so the broker can select the correct auth type. | ||
| * **Host SA auto-detection from metadata (#1482):** Co-located broker registration never set `gcpHostServiceAccountEmail`, breaking GCP identity passthrough on single-node tier. Now auto-detects from GCE metadata server; validator widened to accept `@developer.gserviceaccount.com` (default Compute Engine SA). | ||
| * **Cloud Run sandbox defaults on single-node tier (#1481):** `GetDefaultSettingsDataYAML()` always returned the workstation template, causing "remote (kubernetes)" to appear as the only runtime profile. Now returns the cloudrun-sandbox template when running on that tier. | ||
| * **Antigravity effort flag and thinking tiers (#1479):** Harness crashed on startup with thinking level set — wrong CLI flag (`--thinking-level` → `--effort`) and wrong tier mapping (mixed-case → lowercase matching agy expectations). |
There was a problem hiding this comment.
The term "agy" appears to be a typo for "Antigravity's" or "AG's". Consider correcting this to "Antigravity's" to match the item's title and maintain professional documentation standards.
1 participant
Daily changelog entry for 2026-09-06 (11 PRs).
GCP SM NotFound mapping fix, cold-start super-admin bootstrap, as_needed secret autodetect, host SA auto-detection, Cloud Run sandbox defaults.