Skip to content

feat: upgrade to flutter 3.35.0#1344

Merged
marcossevilla merged 2 commits into
mainfrom
feat/flutter-3.35.x
Aug 25, 2025
Merged

feat: upgrade to flutter 3.35.0#1344
marcossevilla merged 2 commits into
mainfrom
feat/flutter-3.35.x

Conversation

@marcossevilla

Copy link
Copy Markdown
Member

Status

IN DEVELOPMENT

Description

Bumps Dart to 3.9.0 and Flutter to 3.35.0.

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

@marcossevilla marcossevilla self-assigned this Aug 22, 2025
@marcossevilla
marcossevilla marked this pull request as ready for review August 22, 2025 12:41
@marcossevilla
marcossevilla requested a review from a team as a code owner August 22, 2025 12:41
@marcossevilla marcossevilla mentioned this pull request Aug 22, 2025
@marcossevilla
marcossevilla merged commit 215cbdb into main Aug 25, 2025
23 checks passed
@marcossevilla
marcossevilla deleted the feat/flutter-3.35.x branch August 25, 2025 11:21
marcossevilla pushed a commit that referenced this pull request Jan 14, 2026
Fixes #1360

The previous CI verification using `git diff` could not detect new
untracked files added to the brick. This caused PR #1344 to pass CI
with a stale bundle, which was later discovered in PR #1358.

Changes:
- Replace simple `git diff` with comprehensive two-part verification
- Check for both modifications AND untracked/deleted bundle files
- Add bundle file path to workflow triggers for direct changes
- Improve error messages with clear remediation steps

The new verification now catches:
- Modified brick files (existing behavior)
- New brick files added (NEW - fixes the bug)
- Deleted brick files (existing behavior)
- Incorrect output paths (NEW)
- Direct bundle modifications (improved)

This ensures the committed bundle always matches what the current
brick source would generate, preventing silent bundle drift.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants