5 Commits (fea8f62e8aab6382652ca08a533f389bacdd4394)

Author	SHA1	Message	Date
Strycher	2ff190cee1	fix(#322): use PR head SHA in artifact names, not the merge SHA ... Gemini adversarial review caught a real traceability defect. On a `pull_request` event, `github.sha` evaluates to the last merge commit of `refs/pull/N/merge`, not the PR head commit. That merge commit is ephemeral and is not present in branch history, so a PR artifact named with it cannot be traced back to any real commit, which defeats the acceptance criterion this change was written to satisfy. Verified against GitHub's events-that-trigger-workflows reference: "Note that GITHUB_SHA for this event is the last merge commit of the pull request merge branch." Now uses `github.event.pull_request.head.sha || github.sha`, which resolves to the PR head on pull_request events and falls back to the push SHA on pushes to dev/main. Part of epic #312, plan #321 (Phase 1).	2 days ago
Strycher	8ea5ede1dc	chore(#322): upload build artifacts + build on dev pushes ... Two diagnostics faults from #313, fixed together: 1. Dead push trigger. build.yml and flutter_dart.yml declared `push: branches: [main]`, but no `main` branch exists in this repo (default is `dev`), so the push half of every trigger had never fired. Nothing built on merge. Added `dev` to both; `main` is created separately after this merges. 2. No artifacts. All six platform jobs stopped at `flutter build`, so every binary CI produced was discarded with the runner. Added actions/upload-artifact to the four jobs that produce something installable or servable: android build/app/outputs/flutter-apk/app-release.apk windows build/windows/x64/runner/Release/ linux build/linux/x64/release/bundle/ web build/web/ ios and macos are compile checks only and upload nothing: ios is built --no-codesign so it is not installable, and macos is kept as a compile check per the owner's decision on #321. Artifacts carry run number + commit SHA so a build traces back to a commit, and use if-no-files-found: error so a wrong path fails loudly rather than silently publishing an empty artifact. Android artifacts are debug-signed for now; real signing is Phase 5. The web artifact is the plain `flutter build web` output, not the build_pipe versioned build used for deploys; Phase 4 addresses that. Part of epic #312, plan #321 (Phase 1, owner-approved).	2 days ago
Strycher	39274488c3	ci(#227): add windows build job to build.yml ... CI never compiled Windows, the primary test bench (RAK4631 / COM12 / USB serial). Add a windows job mirroring the existing platform jobs: runs-on windows-latest, flutter-action stable, pub get, flutter build windows --release --no-pub. Advisory to start (not in branch-protection required checks); flip to required after 5 green runs (#226). The first run validates the windows-latest env against the local bench (C++ ATL, Developer Mode, llamadart/vulkan, flserial); fixes applied per the #226 plan. Part of #226. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	1 week ago
446564	6070802213	stop building twice for pull requests ... we should only run the build steps on a pull request OR a push to main	6 months ago
Michael Lynch	1726119c3e	Add a Github Action to build code in CI ... This adds a CI workflow in Github Actions to verify that the flutter builds compile for all supported platforms. I tried adding Windows, but it currently fails, so I excluded it from this initial set.	6 months ago