Skip to content

[pull] main from browser-use:main - #665

Merged
pull[bot] merged 3 commits into
17lai:mainfrom
browser-use:main
Aug 18, 2026
Merged

[pull] main from browser-use:main#665
pull[bot] merged 3 commits into
17lai:mainfrom
browser-use:main

Conversation

@pull

@pull pull Bot commented Aug 18, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

The only job in this workflow dispatched a `trigger-workflow` event to
browser-use/cloud using TRIGGER_CLOUD_BUILD_GH_KEY. That token stopped
working after 2026-04-25 — every run since has failed with a 401 "Bad
credentials" on POST /repos/browser-use/cloud/dispatches, so the cloud
eval image has not actually been built from this trigger in ~4 months.

Nothing else references the workflow and it is not a required status
check on main.
`cloud_evals.yml` had exactly one job, `trigger_cloud_eval_image_build`,
which dispatched a `trigger-workflow` `repository_dispatch` event at
`browser-use/cloud` using `secrets.TRIGGER_CLOUD_BUILD_GH_KEY`.

That token stopped working after **2026-04-25**. Every run since fails
within ~10s:

```
RequestError [HttpError]: Bad credentials
status: 401
url: 'https://api.github.com/repos/browser-use/cloud/dispatches'
```

Over the last 200 runs of this workflow: 65 success / 135 failure, with
every failure on the recent side. So this trigger has not built a cloud
eval image in ~4 months, and it has been painting a red X on every push
to `main` and `releases/*` the whole time.

Since the job was the whole workflow, removing it means deleting the
file.

Checks before removing:
- No other file in the repo references `cloud_evals` or
`TRIGGER_CLOUD_BUILD_GH_KEY`.
- Not a required status check on `main` (those are `code-style`,
`syntax-errors`, `type-checker`).

Follow-ups outside this repo, if anyone still wants this build path:
`browser-use/cloud` may still have a `repository_dispatch:
trigger-workflow` listener expecting a `commit_hash` payload, and the
now-invalid `TRIGGER_CLOUD_BUILD_GH_KEY` secret can be deleted from repo
settings.

<!-- This is an auto-generated description by cubic. -->
---
## Summary by cubic
Removes the `cloud_evals` GitHub Actions workflow that triggered Cloud
eval image builds in `browser-use/cloud`. The old job used
`TRIGGER_CLOUD_BUILD_GH_KEY`, which has been invalid since 2026‑04‑25,
causing 401 failures and red X statuses; deleting the workflow stops
those without changing required checks.

**Notes**
- Deletes `.github/workflows/cloud_evals.yml` (job
`trigger_cloud_eval_image_build`).
- Not a required check on `main`; no gating changes.
- Action: delete the `TRIGGER_CLOUD_BUILD_GH_KEY` secret and any
`repository_dispatch: trigger-workflow` listener in `browser-use/cloud`.

<sup>Written for commit 4968ccd.
Summary will update on new commits.</sup>

<a
href="https://cubic.dev/pr/browser-use/browser-use/pull/5491?utm_source=github"
target="_blank" rel="noopener noreferrer"
data-no-image-dialog="true"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source
media="(prefers-color-scheme: light)"
srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img
alt="Review in cubic"
src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a>

<!-- End of auto-generated description by cubic. -->
@pull pull Bot locked and limited conversation to collaborators Aug 18, 2026
@pull pull Bot added the ⤵️ pull label Aug 18, 2026
@pull
pull Bot merged commit 898f23f into 17lai:main Aug 18, 2026
6 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant