Repository navigation
chore(deps): update chromedp/headless-shell docker tag to v152 - #263
Merged
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/chromedp-headless-shell-152.x
branch
6 times, most recently
from
August 27, 2026 15:44
e4dce6d to
f597a02
Compare
renovate
Bot
force-pushed
the
renovate/chromedp-headless-shell-152.x
branch
from
August 27, 2026 19:39
f597a02 to
3a82b40
Compare
fclairamb
enabled auto-merge (squash)
August 27, 2026 19:49
fclairamb
added a commit
that referenced
this pull request
Aug 27, 2026
…n host (#274) Batch branch for 2026-08-27. Two specs implemented end to end, plus the follow-ups that were sitting uncommitted in the working tree and a Renovate rule. ## Incident emails link the check page (spec 06) An incident email showed the check name as bare text in the details table. Checks are usually named after their target host, so Gmail and friends auto-linkified it into `https://<the-host-that-is-down>` — a plausible-looking link strictly worse than the real one. - All **8** incident templates now wrap the name in the conditional anchor the intro paragraphs already used, so the client cannot inject its own link. - Both URL builders (`checkDashURL`, `escalationCheckURL`) build from the check **UID** instead of its slug. That survives a rename between sending and clicking, and drops the nil-slug early return that left the name unlinked. This also upgrades the Slack/Teams/Discord/PagerDuty notifiers, which share `checkDashURL`. - Text parts gained an explicit `Check URL:` line — no anchor can stop auto-linking there, so the real link is made to win instead. - Fixtures re-pinned to UID-shaped URLs, with new assertions proving the Check cell renders an `<a href>` around the name. ## Stale identifiers renamed (spec 05) `check-rate-limit-usage-link` → `check-rate-limit-scheduling-link` and `org:checkRateLimit.viewUsage` → `org:checkRateLimit.reviewScheduling`. Both names still said "usage" after v0.19.0 retargeted that link to the scheduling page — which is what led a previous reader to conclude it was a self-link and write a now-wrong assertion. Translated copy is unchanged in all four locales; only the key moved. A **different** `viewUsage` key in the `statusPages` namespace (`"View plan & usage"`) is genuinely about usage and is deliberately untouched. ## Entitlements follow-ups `ListOrgEntitlementAudits` returns an empty slice rather than nil on both drivers — bun leaves the destination nil when nothing matched, and the list is serialized straight onto the API, so an org with no history marshalled as `null` and every caller had to guard before touching `.length`. Plus follow-ups to the banner and rate-limit helpers, the superadmin editor, the availability strip and their tests. ## Renovate: automerge chromedp/headless-shell Its version *is* the Chrome version, so every ~4-week Chrome release reads as a **major** and gets held by the no-major-automerge rule — #263 was exactly that, a one-line docker tag change awaiting review it did not need. (#263 has since been merged by hand; this stops the next one from queueing up.) Scoped narrowly to this image rather than opening up docker majors in general — a postgres or bun major genuinely can break. It is pinned only in `docker-compose.yml`, and CI's E2E job exercises it on every PR. Follows the existing `goja` exception and sits after the major rule, since Renovate's last match wins. ## Test plan - `make build-backend lint-back test` — green - `make build-dash0` + dash0 lint — green, no new errors against the pre-existing debt - dash0 unit tests 1053/1053 - `entitlements-usage.spec.ts` updated for the rename; authored-not-run locally (the `:4000` devloop is not in `SP_RUNMODE=test`) Each spec was independently audited against its requirements before archiving, not taken on the implementer's word. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR contains the following updates:
151.0.7922.109→152.0.7939.3Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.