feat: track Flutter version in Renovate via Docker datasource #452

Merged
guettlibot merged 1 commits from refs/pull/452/head into main 2026-06-05 20:42:49 +00:00
guettlibot commented 2026-06-05 19:55:40 +00:00 (Migrated from codeberg.org)

Summary

  • Adds a custom Renovate manager that reads the pinned Flutter version from .fvmrc
  • Uses ghcr.io/cirruslabs/flutter as the Docker datasource so Renovate only proposes a bump when the corresponding image tag exists in the registry
  • The CI pipeline (ci/main.go) already derives the Docker image tag from .fvmrc at runtime — .fvmrc is the single source of truth; no other files need grouping

How it works

Renovate checks ghcr.io/cirruslabs/flutter for available tags. If 3.44.1 doesn't exist yet, no PR is opened. Once the image is published, Renovate opens a PR to bump .fvmrc — the only file that needs to change.

Verification

  • renovate.json schema validated
  • Reviewed ci/main.go: FlutterVersion is read exclusively from .fvmrc; no hardcoded version strings elsewhere require additional grouping rules

Closes #447

## Summary - Adds a custom Renovate manager that reads the pinned Flutter version from `.fvmrc` - Uses `ghcr.io/cirruslabs/flutter` as the Docker datasource so Renovate only proposes a bump when the corresponding image tag exists in the registry - The CI pipeline (`ci/main.go`) already derives the Docker image tag from `.fvmrc` at runtime — `.fvmrc` is the single source of truth; no other files need grouping ## How it works Renovate checks `ghcr.io/cirruslabs/flutter` for available tags. If `3.44.1` doesn't exist yet, no PR is opened. Once the image is published, Renovate opens a PR to bump `.fvmrc` — the only file that needs to change. ## Verification - `renovate.json` schema validated - Reviewed `ci/main.go`: `FlutterVersion` is read exclusively from `.fvmrc`; no hardcoded version strings elsewhere require additional grouping rules Closes #447
Sign in to join this conversation.