fix: restore fresh Flutter Apple dependency scanning - #491
Merged
Conversation
leehack
marked this pull request as ready for review
September 8, 2026 13:10
This was referenced Sep 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
Closes #490. Closes #492.
Repairs the merged PR #484 regression: its hook output registered a nonexistent Artifacts directory, causing Flutter 3.47.1 dependency scanning to fail before tests. Track the existing SwiftPM manifest parent instead; hooks_runner directory hashing observes child names, so adding/removing Artifacts invalidates cached success. Exact companion ABI validation and local-override rejection remain unchanged.
The new Unreleased note exposed the separate Web pin checker lifecycle defect #492. Pin-free Unreleased notes now use only the immediately following exact pubspec-version release section. Missing/mismatched sections and stale, malformed, or duplicate current pin claims fail closed. No historical notes were rewritten, and no native/Web/LiteRT pin changes.
Exact-head validation
Head: d7ac6a7. Base: 44ec6b2. Clean worktree, 0 behind / 5 ahead.
High-risk review
Artifact-consumer and regression-policy scope. Zero known PR-caused P1 regressions. Independent exact-head adversarial review and all populated checks are complete. Repository-local readiness is established; external status-publisher governance is unchanged and no configured attestation is claimed. PR remains draft pending maintainer decision.
Preservation and boundaries
Original dirty iPad worktree and draft #489 untouched. No force push, mark-ready, merge, release, publication, workflow_dispatch, environment/settings, pin, or physical-device action. The only manual CI action was the targeted failed Windows job rerun described above.