buildbot/.github, branch v28

ci: run black in --check mode

2026-11-01T10:06:33Z

The lint job ran `black phase1/master.cfg`, which rewrites the file inside the CI checkout and always succeeds. Run it with `--check --diff`, so unformatted code fails the job and the log shows the needed changes. Also run it on phase*/master.cfg, the same files that ruff and flake8 check, so phase2 is covered too. Signed-off-by: Petr Štetiar Link: https://github.com/openwrt/buildbot/pull/84 Signed-off-by: Christian Marangi

ci: bump lint tools and use `ruff check`

2026-11-01T10:06:32Z

Update requirements-dev.txt to the latest releases: black 23.12.1 -> 26.10.1 ruff 0.1.9 -> 0.17.3 flake8 6.1.0 -> 7.4.1 cram 0.7 (unchanged, already the latest) Ruff 0.17 requires the `check` subcommand and expects the settings in .ruff.toml under a `lint` table, so update both. Ruff 0.17 also enables more rules by default and reports 58 style findings in the master.cfg files, mostly percent-format to str.format conversions. The configs have no tests, so rewriting them is not worth the risk. Select the previous default rules (E4, E7, E9, F) explicitly instead. flake8 needs no changes. Signed-off-by: Petr Štetiar Link: https://github.com/openwrt/buildbot/pull/84 Signed-off-by: Christian Marangi

ci: run test-lint on Python 3.13

2026-11-01T10:06:31Z

The containers are now based on Debian 13, which ships Python 3.13. Run the lint job with the same version instead of 3.11. Signed-off-by: Petr Štetiar Link: https://github.com/openwrt/buildbot/pull/84 Signed-off-by: Christian Marangi

CI(deps): Bump docker/metadata-action from 5 to 6

2026-06-09T13:53:43Z

Bumps [docker/metadata-action](https://github.com/docker/metadata-action) from 5 to 6. - [Release notes](https://github.com/docker/metadata-action/releases) - [Commits](https://github.com/docker/metadata-action/compare/v5...v6) --- updated-dependencies: - dependency-name: docker/metadata-action dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot]

ci: fix missing tag on containers on git tag pushes

2026-01-13T16:49:33Z

Non semver tags like v26 were not included in metadata output, so image pushes only produced sha- tags. Add tag reference metadata so tag pushes publish a matching container tag. ##[warning]v26 is not a valid semver. More info: https://semver.org/ ##[group]Docker tags ghcr.io/openwrt/buildbot/buildmaster-v3.11.8:sha-f2c82f2 Fixes: 93918cc2e225 ("ci: add support for testing PR containers") Signed-off-by: Petr Štetiar

ci: remove cleanup-pr-containers workflow

2026-01-13T16:48:57Z

It needs a bit more time to debug this properly. Signed-off-by: Petr Štetiar

ci: fix workflow_dispatch on PRs by using local context for docker buildx

2026-01-11T21:56:56Z

Without explicit context, docker/build-push-action defaults to fetching from the GitHub repository using github.sha as the ref. For workflow_dispatch events, github.sha points to the default branch (main), not the checked-out PR ref. This caused PR container builds to contain main branch code instead of the PR changes. With `context: .` makes Docker build uses the locally checked-out files from refs/pull/{N}/merge. The issue was identified by inspecting the workflow run logs which showed: docker buildx build ... https://github.com/openwrt/buildbot.git#93918cc2e2257ae8838166d2baad30617295df4e The #93918cc2... ref at the end is the main branch SHA, not the PR merge commit. This is the default behavior when context is not specified - the action uses ${{ github.server_url }}/${{ github.repository }}.git#${{ github.sha }} Signed-off-by: Petr Štetiar

ci: avoid branch tags on workflow_dispatch

2026-01-11T20:52:57Z

Currently workflow_dispatch pushes branch tags, so lets fix it by disabling branch tagging for dispatch runs. Signed-off-by: Petr Štetiar

ci: rename OPENWRT_VERSION to BUILDBOT_CONFIG_SHA

2026-01-11T20:52:45Z

The old name was misleading as it suggested an OpenWrt release version. The variable holds the git SHA of this buildbot config repository, used for quick URL links to the configuration commit. Signed-off-by: Petr Štetiar

ci: add container version tag to BUILDWORKER_DESCRIPTION

2026-01-11T20:52:36Z

Add CONTAINER_TAG build argument to indicate whether the container was built from a tag (v25), PR (pr-73), or branch (main). This makes it easier to identify which version of the container is running. While at it, drop Docker prefix to make it shorter. Signed-off-by: Petr Štetiar