Align with docker-flutter-sdk pattern: check release existence via
HTTP status code (no auth needed), reserve GITEA_TOKEN for release
creation only.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- apko release assets use lowercase OS and Go arch naming
(linux_amd64), but uname returns Linux and x86_64. Map with
tr/sed before building the download URL.
- Flutter release check used curl -fsSL which fails on 404 when
the release doesn't exist yet. Switch to -sS so the step
continues and correctly detects new versions.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Rename flutter variant to flutter-sdk for clarity across all configs
and pipelines
- Add curl to dotnet-runtime apko config (needed to bootstrap .NET
runtime installation in downstream Dockerfiles)
- Add daily update-check pipeline that monitors Flutter stable channel
and Wolfi package updates, auto-creates releases for new Flutter
versions and rebuilds all variants with latest packages
Tested all variants with real workloads:
- dotnet-sdk: dotnet new console + build + run
- dotnet-runtime: multi-stage build, run prebuilt app
- flutter-sdk: flutter create + build web --release
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>