29c4f74ef5
Workflows used subosito/flutter-action with no version, silently tracking GitHub's latest stable. When stable rolled to 3.44.1 it broke the build with no code change. Pin explicitly so builds are reproducible and Flutter upgrades are a deliberate bump rather than a surprise. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
21 lines
488 B
YAML
21 lines
488 B
YAML
name: CI
|
|
on:
|
|
push:
|
|
branches: [main]
|
|
jobs:
|
|
test:
|
|
name: Check and test on ${{ matrix.os }}
|
|
runs-on: ${{ matrix.os }}
|
|
strategy:
|
|
matrix:
|
|
os: [ubuntu-latest, windows-latest, macos-latest]
|
|
steps:
|
|
- uses: actions/checkout@v6
|
|
- uses: subosito/flutter-action@v2
|
|
with:
|
|
flutter-version: 3.44.1
|
|
cache: true
|
|
- run: flutter doctor -v
|
|
- run: flutter pub get
|
|
- run: flutter analyze
|
|
- run: flutter test
|