Skip to content

chore: back-merge v0.11.1 into next - #116

Open
ravenflight-releases[bot] wants to merge 3 commits into
nextfrom
backmerge/v0.11.1
Open

ravenflight-releases[bot] wants to merge 3 commits into
nextfrom
backmerge/v0.11.1

Conversation

@ravenflight-releases

Copy link
Copy Markdown
Contributor

Brings the v0.11.1 version bump and changelog from main into next. Merge with a merge commit, not a squash, so the branches share history.

taraxvoid and others added 3 commits October 2, 2026 13:54
With `single-environment: true`, soundry and synthomaha now run
`test:e2e:lighthouse` on `main`, and the runner fails on GitHub runners:
`FATAL: zygote_host_impl_linux.cc: No usable sandbox! ... Ubuntu 23.10+
... AppArmor disabled unprivileged user namespaces`. The runner had
never executed on a runner before (it only ran on PRs into `live`, which
these sites never open).

On Linux with `CI` set, the runner now points `CHROME_PATH` /
`PUPPETEER_EXECUTABLE_PATH` at a small wrapper script that execs Chrome
with `--no-sandbox`. Callers change nothing; it only applies in CI,
where the browser loads our own static build. Opt out with
`VOIDFLOW_CHROME_SANDBOX=1`.

Unit tests cover the wrapper (executable, argument order, paths with
spaces/quotes). Validating on a real runner via a caller PR next; will
report the result here.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
🤖 I have created a release *beep* *boop*
---


##
[0.11.1](v0.11.0...v0.11.1)
(2026-10-02)


### Bug Fixes

* **unlighthouse:** launch Chrome with --no-sandbox in CI
([#114](#114))
([67daebb](67daebb))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: ravenflight-releases[bot] <330165707+ravenflight-releases[bot]@users.noreply.github.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant