- Note: We could always use more contributors, testers, etc. E.g.:
- A dedicated maintainer for the NixOS stable channel
- PRs with cleanups, improvements, fixes, etc. (but please try to make reviews as easy as possible)
- People who handle stale issues/PRs
- Primary maintainer (responsible for all updates): @primeos
- Testers (test all stable channel updates)
- Stable channel:
- Other relevant packages:
chromiumDev: For testing purposes only (not build on Hydra). We use these channels for testing and to fix build errors in advance so that
chromiumupdates are trivial and can be merged fast.
google-chrome-dev: Updated via Chromium's
chromedriver: Updated via Chromium's
upstream-info.jsonand not built from source.
- Source code: https://source.chromium.org/chromium/chromium/src
- Bugs: https://bugs.chromium.org/p/chromium/issues/list
- Release updates: https://chromereleases.googleblog.com/
upstream-info.json. After updates it is important to test at least
nixosTests.chromium (or basic manual testing) and
Note: The source tarball is often only available a few hours after the release was announced. The CI/CD status can be tracked here:
To run all automated NixOS VM tests for Chromium, ungoogled-chromium, and Google Chrome (not recommended, currently 6x tests!):
A single test can be selected, e.g. to test
nixos/tests/chromium.nix for all available options):
nix-build nixos/tests/chromium.nix -A ungoogled
(Note: Testing Google Chrome requires
For custom builds it's possible to "override"
All updates are considered security critical and should be ported to the stable
channel ASAP. When there is a new stable release the old one should receive
security updates for roughly one month. After that it is important to mark
Chromium as insecure (see 69e4ae56c4b for an example; it is important that the
tested job still succeeds and that all browsers that use
are marked as insecure).
Major version updates
Unfortunately, Chromium regularly breaks on major updates and might need various patches. Either due to issues with the Nix build sandbox (e.g. we cannot fetch dependencies via the network and do not use standard FHS paths) or due to missing upstream fixes that need to be backported.
Good sources for such patches and other hints:
If the build fails immediately due to unknown compiler flags this usually means that a new major release of LLVM is required.
Beta and Dev channels
Those channels are only used to test and fix builds in advance. They may be broken at times and must not delay stable channel updates.
- Version: chrome://version/
- GPU acceleration: chrome://gpu/
- Essential functionality: Browsing, extensions, video+audio, JS, ...
- WebGL: https://get.webgl.org/
- VA-API: https://wiki.archlinux.org/index.php/chromium#Hardware_video_acceleration
- Optional: Widevine CDM (proprietary), Benchmarks, Ozone, etc.