From 3511e5c8f1ecd8e9ff119f3292afce84fa85a15d Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Fri, 10 Jul 2026 16:58:04 +0100 Subject: [PATCH] Publish platform-specific Flutter captures --- .github/workflows/runtime.yml | 6 +++--- README.md | 4 +++- pubspec.yaml | 2 +- 3 files changed, 7 insertions(+), 5 deletions(-) diff --git a/.github/workflows/runtime.yml b/.github/workflows/runtime.yml index 9b8226c..98d0fbd 100644 --- a/.github/workflows/runtime.yml +++ b/.github/workflows/runtime.yml @@ -25,8 +25,8 @@ jobs: - name: Analyze run: flutter analyze lib test - - name: Test responsive runtime captures - run: flutter test + - name: Test and generate Linux runtime captures + run: flutter test --update-goldens - name: Verify lifecycle shell: pwsh @@ -35,6 +35,6 @@ jobs: - name: Upload golden captures uses: actions/upload-artifact@v7 with: - name: eveflutter-captures-${{ github.sha }} + name: eveflutter-linux-captures-${{ github.sha }} path: test/goldens/*.png if-no-files-found: error diff --git a/README.md b/README.md index 9fbe435..b2f8f71 100644 --- a/README.md +++ b/README.md @@ -5,9 +5,11 @@ Flutter projection, provider selection, command-intent construction, platform build glue, tests, and captures. Providers retain state and command authority; plugins retain domain semantics. -The `eveflutter-v1.0.1` release is owner-built. CI analyzes the runtime, runs +The `eveflutter-v1.0.2` release is owner-built. CI analyzes the runtime, runs the responsive capture suite, verifies lifecycle evidence, and publishes the committed golden captures as a commit-keyed artifact. +Linux CI regenerates Linux goldens rather than byte-comparing them with Windows +captures; widget and contract assertions remain shared across platforms. Current smoke target: diff --git a/pubspec.yaml b/pubspec.yaml index c70fd7f..c30d3fa 100644 --- a/pubspec.yaml +++ b/pubspec.yaml @@ -14,7 +14,7 @@ publish_to: 'none' # Remove this line if you wish to publish to pub.dev # https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html # In Windows, build-name is used as the major, minor, and patch parts # of the product and file versions while build-number is used as the build suffix. -version: 1.0.1+2 +version: 1.0.2+3 environment: sdk: ^3.12.1