Release v1.11.0 #822
Merged
Release v1.11.0 #822
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR contains the following updates: | Update | Change | |---|---| | lockFileMaintenance | All locks refreshed | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. 🔧 This Pull Request updates lock files to use the latest dependency versions. --- ### Configuration 📅 **Schedule**: Branch creation - "before 4am on monday" in timezone Europe/London, Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://redirect.github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/overmindtech/workspace). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi4xNi4xIiwidXBkYXRlZEluVmVyIjoiNDIuMTkuOSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiZGVwZW5kZW5jaWVzIl19--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> GitOrigin-RevId: a171dad7a43b7c06765ee61e195be62e888b47f0
This now establishes a clear and early translation from the user-level config, where "link depth" makes sense as it is the word used everywhere else into the algorithm-level "max blast radius" wording that is relevant for the implementation. Also: * rename inconsistent usages throughout the code, especially in area51 * remove unused max items codepath * remove unused param from changes_test.go * align defaults throughout * improve docs at the proto level <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Consolidates blast radius depth settings to `BlastRadiusMaxRecursionDepth` across backend, admin UI, and tests, removing old `linkDepth`/`maxDepth` plumbing and mapping config `linkDepth` to recursion depth. > > - **Backend**: > - Replace `BlastRadiusLinkDepth` with `BlastRadiusMaxRecursionDepth` in `ChangeAnalysisCalculationArgs` and all query calls (`LinkDepth` now uses recursion depth). > - In `StartChangeAnalysis`, translate account/config `linkDepth` to recursion depth for v5/v6; remove separate `blastRadiusLinkDepth` var. > - Set worker default `BlastRadiusMaxItems` to `1000`; drop job args for link depth/max items and related queue params. > - **Admin UI (Area51)**: > - Update blast-radius form to use `blastRadiusMaxRecursionDepth` (default 10); remove `maxDepth`, `blastRadiusLinkDepth`, and `blastRadiusMaxItems` inputs/handling. > - Adjust job queuing to pass only recursion/concurrency/goroutine/time params. > - **Tests**: > - Migrate usages from link depth to recursion depth; update helper `createTestItem` signature. > - Minor log text tweaks. > - **Proto/SDK docs**: > - Clarify `BlastRadiusConfig.linkDepth` comments (max levels traversed); regenerate Go/TS outputs. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 32ae7c7e697f33e008a4dff98af7fd5ed586ae20. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> GitOrigin-RevId: 7af0aef4af122040601dd43ae3b9ec9cd6659d57
This also addresses [ENG-1912](https://linear.app/overmind/issue/ENG-1912/gcp-adapters-marked-with-indevelopment-true-appear-in-possible-links) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Fixes the Vercel docs build by adding Prettier formatting, updating Docusaurus/lychee config, and filtering/sorting GCP potential links; also adds new resource types and wide-ranging docs/link cleanups. > > - **Build/Tooling**: > - Add Prettier formatting step to `generate-docs.sh`. > - Update Docusaurus config and lychee remap (cloud.google.com → docs.cloud.google.com). > - **GCP Source**: > - Filter `potentialLinks` to only valid, documented adapters and sort them deterministically (`generate-json.go`, `dynamic/shared.go`). > - **Content/Docs**: > - Add new types: `lambda-event-source-mapping`, `gcp-big-query-routine`, `gcp-compute-machine-type`. > - Widespread markdown fixes (lists, tables, code fences), typo corrections, and JSON `potentialLinks` adjustments (ordering/removal of invalid links). > - Numerous GCP/AWS/K8s doc tweaks for consistency and accuracy. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 3f15167e684af373c4341ac56f05781fd2f88851. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> GitOrigin-RevId: 16def771fabca709e1c0bd682fcf7e7239c7e84e
waiting for https://linear.app/overmind/issue/ENG-1832/setup-a-test-account-in-azure-that-everyone-can-access to finish to start testing GitOrigin-RevId: 1b045c858dd6c49e228c04a3fb6b53cb4c1e81c5
With manual testing using `otel-cli` ``` / # otel-cli exec --verbose --endpoint http://otelcol-node-opentelemetry-collector.otel.svc.cluster.local:4318 -n "test data" -s "kubernetes-metrics" echo foo ``` * [Honeycomb](https://ui.honeycomb.io/overmind/environments/test/datasets/kubernetes-metrics/result/k46h7rhGgvV?expd_asc=true&expd_back=true&expd_col=_hny.ts&expd_fwd=false&expd_id=wBjtxgo3Xae&expd_page=250&tab=explore&vs=hideCompare) <img width="331" height="202" alt="2025-12-03_115404+0100_331x202" src="https://github.com/user-attachments/assets/585a1b3f-840b-4749-9997-64c1d980449f" /> * [dash0](https://app.dash0.com/traces/explorer?org=ffae8a0f-44da-409c-aa3a-2fafeff80fde&s=eJx9UM1OAjEQfpeeWSm_mk04IBg0ijFm5cBt2E6xodsubRckZN_dzoJoNPHWzny_c2Rtlh6ZgAAeA0uZsGtprWAtJm1eeRSZKvAVzBoJF35-pLNFZHR5d5B0ugnvZR2e9nk64Fec82WUCPbvvpfy875usQIDkJTy43BrKyPAHb6lJWiPJ5XmWdeRco41rRwEZc0ljfg9OGmQV2cwvD7J8H88LzbRo6EGV5FlpLSDgxw9oXwJ5kn5MLFGqjVNIA9qhwuF-wdBBwT_zpNd_CaE9YlACZUOVNeWaC4mK8g3b06z1FRax3iwimy7Q0dcOh55kmx2KGMhtoeALnJ13KnGCV_uN735dvF8N_rCNxHkfGZmk_F0KfVgnt1shx775Xg0ogjnKm38KLV16KgBaizQhEdliE2pWV1_ArFEr98%3D) <img width="790" height="633" alt="2025-12-03_115433+0100_790x633" src="https://github.com/user-attachments/assets/ea5a89b1-a5ce-4e3e-a13d-a5b3c55c6077" /> GitOrigin-RevId: 19686232b25cdda6e62f0dfa614a784d2bcf74e4
GitOrigin-RevId: e7a5a3088646f4650f2d23b6f1cbb03bef33d22f
GitOrigin-RevId: 8e10f5c23bdfcb9cae58adefad44add5aa36afc8
<img width="2862" height="285" alt="image" src="https://github.com/user-attachments/assets/0a21bada-58e0-47a6-b628-1e9bf0b4d48a" /> manual testing <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Adds label support to changes: persisted as JSONB, marshaled in models/server, exposed in API responses/updates, and settable via CLI `--labels` flag, with comprehensive tests. > > - **Backend / Models & DB**: > - Store `labels` in `changes` table; include in `CREATE`/`UPDATE` with `COALESCE(@labels::jsonb, '[]'::jsonb)`. > - Update sqlc params/structs to include `labels` bytes and return `labels` in queries. > - Extend `Change.ToSDP`/`ToSummary` and `ToUpdate` to handle `labels` via `UnmarshalLabels`/`Labels`. > - Implement `MarshalLabels` and improve `UnmarshalLabels` for protobuf `sdp.Label` arrays. > - **Server / API**: > - `CreateChange`/`UpdateChange` marshal and persist `properties.labels`; include in responses and markdown via `getLabelsLine`. > - **CLI**: > - Add `--labels` flag; implement `parseLabelsArgument()` with hex colour validation; include `labels` in `ChangeProperties` for `submit-plan` and `terraform plan` flows. > - **Tests**: > - Add model tests for label marshal/unmarshal; server tests for creating/updating changes with multiple labels; CLI tests for label parsing and validation. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 5c3a8ccb633563de91a882beaf18f017bb2fa00a. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> GitOrigin-RevId: 7cfbe31693584c81c504419c71de65187a16a495
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Copybara Sync - Release v1.11.0
This PR was automatically created by Copybara, syncing changes from the overmindtech/workspace monorepo.
Original author: TP Honey ([email protected])
What happens when this PR is merged?
tag-on-mergeworkflow will automatically create thev1.11.0tag on mainReview Checklist