build(deps-dev): bump chromedriver from 146.0.5 to 146.0.6 - #591
build(deps-dev): bump chromedriver from 146.0.5 to 146.0.6#591dependabot[bot] wants to merge 2 commits into
Conversation
Bumps [chromedriver](https://github.com/giggio/node-chromedriver) from 146.0.5 to 146.0.6. - [Commits](giggio/node-chromedriver@146.0.5...146.0.6) --- updated-dependencies: - dependency-name: chromedriver dependency-version: 146.0.6 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Agent QA review — interactive + visual diff (advisory, non-blocking)Last updated Aug 26, 2026, 1:12 AM PDT · new commit pushed · commit 0 open · 0 resolved · visual diff 42.31% · verdict PASS Open findings
What the agent checkedTested https://business.adobe.com/resources/main.html with PR #591's CaaS build injected (PR only bumps the chromedriver dev-dependency used for Selenium test tooling — no frontend/production source files were touched). What I checked:
Conclusion: This PR only updates a devDependency (chromedriver, used for Selenium-based test automation) and contains zero changes to application/CaaS source code. Functionally and visually the live page behaves identically to what's expected of stable business.adobe.com — filtering, result counts, and card rendering all work correctly. The large visual diff percentage reported for this PR is attributable to dynamic/rotating content on the page (carousel, personalized cards, chat widget) rather than any actual code change from this dependency bump. No regressions found. PR / stable / diff screenshots + console + axe artifacts in the workflow run. Review history (1 run)
|
AI Code ReviewLast updated Aug 26, 2026 1:14 AM PDT · new commit pushed · commit 0 open · 0 resolved Open findingsNo open findings. ✅ Review history (1 run)
|
… QA failing silently The proxy now rejects requests without x-session-id (HTTP 403 missing_required_header). Only qa-runner-v2.mjs sent it, so Agent QA Review kept working while every direct caller started 403ing. On PR #591 that killed feature-review.mjs at its first LLM call: three 403s, llm failed after retries, and the top-level catch exited 0. Green job, no comment - even though build-output-diff had already published NO_CHANGE and review-score-gate had auto-passed the PR. - add x-session-id to all eight direct proxy callers - feature-review.mjs: fall back to postNonInjectable when the triage model is unavailable, so the deterministic bundle-diff verdict is still reported (it is a REST status read, it never needed a model) - feature-review.mjs: write FEATURE_REVIEW_FAILED on an unhandled error - qa-feature-review.yml: log that marker to the shared monitor issue, mirroring qa-agent-review.yml, so a silent outage is visible Claude-Session: https://claude.ai/code/session_01QimdQaYPSvXAaSDAssrfK1
|

0 New Issues
0 Fixed Issues
0 Accepted Issues
No data about coverage (77.70% Estimated after merge)
Bumps chromedriver from 146.0.5 to 146.0.6.
Commits
2d895e0Bump version to 146.0.6Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)