Repository navigation
Fix the three red CI checks: Anthropic 2.x in the agent tests, the Chromium enter-text launches, and a React teardown - #863
Open
davidmckayv wants to merge 4 commits into
Open
davidmckayv wants to merge 4 commits into
davidmckayv wants to merge 4 commits into
Conversation
…raph AG-UI test anthropic 2.x sends the key as Authorization: Bearer instead of x-api-key and dates its Messages API version later than 2023-06-01. The provider-boundary test asserted both by their 1.x values, so it failed once the unpinned requirements resolved 2.x. It now reads the key from either header and checks the version is a date; the endpoint, key, model and body it asserts are unchanged.
CI installs Chromium with --no-shell since #829, and enter-text launched Playwright's default, the separate headless shell, so it failed to start. It now launches channel "chromium", the build the computer itself launches.
davidmckayv
requested review from
MikeRyanDev,
guidovizoso,
mxmzb and
tylerslaton
as code owners
October 28, 2026 01:39
Anthropic's SDK 2.3.0, which CI now installs for the AG2 harness, sends the key as Authorization: Bearer instead of x-api-key. The agent's key still reaches Anthropic; the test only looked for the old header, so it failed on every pull request. It now accepts either, and passes with Anthropic's SDK 1.17.0 and 2.3.0 alike. (cherry picked from commit a1391e7)
The Dismiss save settles a render after the last test returns, and afterAll unregistered happy-dom first, so the render fired against a missing document and bun reported an unhandled error between tests: zero failures, a red job. afterAll now awaits settleReactWork first, as the other React tests do.
davidmckayv
changed the title
This branch has not been deployed
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
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.
What this changes
Three CI checks are red on
mainand on every open PR. None of them is caused by product code.python harness regressions: the agents' requirements are unpinned, and they now resolve
anthropic2.x. That SDK sends the key asAuthorization: Bearerinstead ofx-api-key, and dates its Messages API version later than2023-06-01.agent-langgraph-agui/tests/test_provider_boundaries.pyasserted both by their 1.x values. It now reads the key from either header and checks that the version is a date. The endpoint, key, model and body it asserts are unchanged. This PR also carries Read the Anthropic key from either header in the AG2 test #859's identical AG2 commit, so it is green on its own and merges cleanly whichever lands first.main's run stops at AG2, which is why the LangGraph failure hadn't shown there yet.computer (real browser): since fix(computer): install only the Chromium build the computer launches #829, CI installs Chromium with
--no-shell.agent-computer/tests/enter-text.test.tslaunched Playwright's default build, the separate headless shell, which is no longer on the runner, so it never started. It now launcheschannel: "chromium", the build the computer itself launches.tests (unhandled error between tests):
app/tests/self-host-banner.test.tsxunregistered happy-dom while the Dismiss save still had a render posted. That render fired against a missing document, so bun reported zero failures and a red job.afterAllnow awaitssettleReactWork()first, as the other React tests do (seeapp/tests/settle-react-work.ts).Local results: the LangGraph AG-UI suite passes (90, on
anthropic2.3.0),enter-textpasses (5), and the banner tests pass three runs out of three. The flake itself only reproduced on CI.Where it runs
Boundary and audit
Changelog