chore(global): upgrade flutter version and deps

[Jaaco]

Description

Upgrade flutter to newest version, commit updated dependencies.

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
• 🧪 Tests

Summary by CodeRabbit

• Chores
  • Updated Flutter framework to version 3.41.0-stable
  • Updated minimum supported macOS version to 10.15, which establishes new system requirements for macOS users

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated Flutter SDK to version 3.41.0-stable and raised the minimum macOS deployment target from 10.14 to 10.15 across the iOS project configuration, Podfile, and build settings.

Changes

Cohort / File(s)	Summary
Flutter SDK Version Update .tool-versions	Updated Flutter from 3.35.5-stable to 3.41.0-stable.
macOS Platform Target Updates apps/flites/macos/Podfile, apps/flites/macos/Runner.xcodeproj/project.pbxproj	Updated macOS deployment target from 10.14 to 10.15 in platform declaration and XCBuildConfiguration sections (Debug, Release, Profile configurations).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• feat: reusable build workflow for macos #65: Modifies the same macOS configuration files (Podfile and project.pbxproj) with related platform version updates.

Suggested labels

Needs Attention

Poem

🐰 A hop toward the future bright,
Flutter soars to newer height,
macOS bounds from ten-fourteen past,
Platform targets move at last!
Compatibility checked, all systems go—
Version dance, and update flow! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title describes the main change: upgrading Flutter version and dependencies, which is confirmed by the changeset showing Flutter version bump from 3.35.5 to 3.41.0 and macOS platform updates.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/jaco/upgrade-versions

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.tool-versions:
- Line 1: CI workflows and README still pin Flutter to "3.35.5" while
.tool-versions uses "3.41.0-stable"; search for the string "3.35.5" in the
workflow files (windows_build.yaml, web_build.yaml, validate.yaml,
debian_build.yaml, appimage_build.yaml) and update those pins to
"3.41.0-stable", and also update the README's stated Flutter requirement to
"3.41.0-stable" so all CI and docs match .tool-versions.

---

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 351fbb4 and 4db61c3.

⛔ Files ignored due to path filters (1)

• apps/flites/macos/Podfile.lock is excluded by !**/*.lock

📒 Files selected for processing (3)

• .tool-versions
• apps/flites/macos/Podfile
• apps/flites/macos/Runner.xcodeproj/project.pbxproj

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== .tool-versions =="
cat .tool-versions

echo
echo "== Flutter version pins in CI/workflows =="
fd -HI -t f '.*\.(yml|yaml)$' .github/workflows 2>/dev/null \
  | xargs -r rg -nP 'flutter(-version)?\s*:|subosito/flutter-action|fvm|[0-9]+\.[0-9]+\.[0-9]+(-stable)?'

echo
echo "== FVM-related config/version pins (if any) =="
fd -HI -t f 'fvm_config\.json|\.fvmrc|pubspec\.yaml|README\.md' \
  | xargs -r rg -nP 'flutter|fvm|[0-9]+\.[0-9]+\.[0-9]+(-stable)?'

Repository: marqably/flites

Length of output: 4075

---

Update Flutter version pins in all CI workflows to match .tool-versions.

CI workflows are pinned to 3.35.5, but .tool-versions specifies 3.41.0-stable. This divergence will cause local builds (via FVM/asdf) to use version 3.41.0-stable while CI pipelines run 3.35.5, creating inconsistent build environments.

Update required in:

• .github/workflows/windows_build.yaml (line 66)
• .github/workflows/web_build.yaml (line 60)
• .github/workflows/validate.yaml (line 21)
• .github/workflows/debian_build.yaml (line 62)
• .github/workflows/appimage_build.yaml (line 55)
• README.md (line 61, update version requirement)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.tool-versions at line 1, CI workflows and README still pin Flutter to
"3.35.5" while .tool-versions uses "3.41.0-stable"; search for the string
"3.35.5" in the workflow files (windows_build.yaml, web_build.yaml,
validate.yaml, debian_build.yaml, appimage_build.yaml) and update those pins to
"3.41.0-stable", and also update the README's stated Flutter requirement to
"3.41.0-stable" so all CI and docs match .tool-versions.

[BenAuerDev]

LGTM. But we should update the flutter version also in the build files.

Coderabbit mentioned it above