4 Commits

Include renames

Author	SHA1	Message	Date
randy	4c95927231	Pin check/renovate back to brick-build now that its image has Node ... The runner's label-to-image mapping got repointed at Gitea's own official runner image (docker.gitea.com/runner-images:ubuntu-latest, has Node out of the box) — the earlier opensuse/leap:16.0 mapping for brick-build specifically was what broke check/renovate on 2026-09-12, not brick-build the label itself. Back to pinning both to this machine specifically instead of whichever runner answers to the shared ubuntu-latest label.	2026-09-13 12:32:14 +02:00
randy	c894706140	Revert check/renovate to ubuntu-latest — brick-build's image has no Node ... brick-build's job container (opensuse/leap:16.0) has no Node.js, and every step in check/renovate (checkout, setup-ruby, setup-node) is a JS-based Action that needs it just to start — both runs since the brick-build switch failed immediately, and deploy never ran because it depends on check passing. ubuntu-latest is shared with "Gitea Runner on Cube" (not pinned to this specific machine), but that's fine: only deploy (a unique label held by just brick's native runner) actually needs to land on a specific box.	2026-09-12 21:39:21 +02:00
randy	237e5b2e54	Move check/renovate onto brick-build, deploy stays brick-host ... Renovate no longer needs Docker access for a one-shot docker-run job: switched to setup-node + npm install -g renovate (matching labelprint's workflow), so it fits the same brick-build runner as check instead of the stale "deploy" label. Also note down the build-log readability/API gaps flagged from a real failed terrain build.	2026-09-12 19:36:08 +02:00
randy	3fbd97a0bd	Add a weekly Renovate workflow for dependency updates ... Runs renovate/renovate against this Gitea instance on the native deploy runner, opening PRs for outdated Bundler dependencies instead of relying on manually noticing (as happened with puma/mustermann earlier).	2026-08-27 19:31:24 +02:00