From: Shan Shaji <s.shaji@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH proxmox{_login_manager,_dart_api_client}/pve_flutter_frontend 0/9] chore: bump flutter version to v3.47
Date: Fri, 30 Oct 2026 13:06:08 +0100 [thread overview]
Message-ID: <20261030120617.56692-1-s.shaji@proxmox.com> (raw)
Upgrade Flutter to the latest stable release
What's new: https://flutter.dev/blog/whats-new-in-flutter-3-47
breaking changes: https://docs.flutter.dev/release/breaking-changes#released-in-flutter-3-47
* The decoupled material_ui and cupertino_ui packages have
officially reached v1.0 on pub.dev. We can opt-in to the decoupled
design system by running the following command:
`dart fix --apply --code=migrate_design_widgets`
Running this updates the imports across all files. Since this results
in too many file changes, it will be sent as a separate patch.
* Another notable change is the migration to built-in Kotlin support.
Starting from AGP 9.0, built-in Kotlin support is enabled unless
explicitly opted out. Flutter suggests migrating apps to AGP 9 and
enabling built-in Kotlin support. However, flutter_inappwebview [1]
and biometric_storage [2] do not yet have stable releases with these
migration changes (only pre-release versions are available).
Additionally, cupertino_http has not yet migrated and lacks stable
or pre-release versions. I have created a PR to remove the explicit
apply of KGP [3] upstream, but have not received feedback yet.
Theoretically, we could upgrade AGP to 9.0 and perform the migration
mentioned in [0], because the Flutter Gradle Plugin applies KGP if
`android.BuiltinKotlin` is false and no KGP application is found [4].
However, other changes in AGP 9 breaks the build due to legacy APIs in
flutter_inappwebview and biometric_storage. Because of this, I
am not migrating the Gradle file, AGP, or Kotlin versions yet.
I will migrate the .gradle file and update the plugins in a
separate series once stable releases are available, or adopt
pre-release versions if Flutter drops support for opt-in flags (which
will likely only happen by the Flutter v3.50 release [5]).
* Another change involves migrating to the Swift Package Manager instead
of CocoaPods, as CocoaPods is now in maintenance mode [6].
cupertino_http [7] has already migrated to SwiftPM, but it was
released as a major version bump, so upgrading it will be handled in a
separate patch. Similarly, flutter_inappwebview and
biometric_storage have pre-release versions with SwiftPM support,
but avoiding them for now as these releases includes other
changes which requires it's own testing. This is safe to do because
Flutter falls back to CocoaPods for any plugins that do not yet
support SwiftPM [7].
- [0] https://docs.flutter.dev/release/breaking-changes/migrate-to-built-in-kotlin/for-app-developers
- [1] https://pub.dev/packages/flutter_inappwebview/versions/6.2.0-beta.3/changelog#620-beta3
- [2] https://pub.dev/packages/biometric_storage/versions/6.0.0-dev.7/changelog#600-dev1
- [3] https://github.com/dart-lang/http/pull/2042
- [4] https://docs.google.com/document/d/1iAMVVvsHqs130hc3-49sstv7n63TgM5aUd-cqAGWHfc/edit?pli=1&tab=t.0#heading=h.4cojipea00cf
- [5] https://github.com/flutter/flutter/issues/189235
- [6] https://blog.cocoapods.org/CocoaPods-Support-Plans/
- [7] https://docs.flutter.dev/packages-and-plugins/swift-package-manager/for-app-developers#how-to-turn-on-swift-package-manager
pve_flutter_frontend:
Shan Shaji (7):
chore: ios: add SwiftPM support
chore: update Gradle, AGP and Kotlin versions
chore: add opt-out flags for built-in Kotlin and Gradle Kotlin DSL
chore: include non-Dart files to analyzers's exclude directive
chore: run `flutter pub upgrade` with flutter (v3.47)
chore: use caret syntax instead of any for shared_preferences plugin
chore: bump minimum supported OS version to 15
analysis_options.yaml | 9 +
android/gradle.properties | 4 +
.../gradle/wrapper/gradle-wrapper.properties | 2 +-
android/settings.gradle | 4 +-
ios/Podfile | 2 +-
ios/Podfile.lock | 17 +-
ios/Runner.xcodeproj/project.pbxproj | 28 +-
.../xcshareddata/xcschemes/Runner.xcscheme | 18 ++
pubspec.lock | 256 +++++++++---------
pubspec.yaml | 2 +-
10 files changed, 195 insertions(+), 147 deletions(-)
proxmox_login_manager:
Shan Shaji (1):
chore: run flutter pub upgrade
analysis_options.yaml | 3 +
pubspec.lock | 216 ++++++++++++++++++++++--------------------
2 files changed, 115 insertions(+), 104 deletions(-)
proxmox_dart_api_client:
Shan Shaji (1):
chore: run flutter pub upgrade
pubspec.lock | 190 +++++++++++++++++++++++++++++----------------------
1 file changed, 107 insertions(+), 83 deletions(-)
Summary over all repositories:
13 files changed, 417 insertions(+), 334 deletions(-)
--
Generated by git-murpp 0.8.1
next reply other threads:[~2026-10-30 12:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 12:06 Shan Shaji [this message]
2026-10-30 12:06 ` [PATCH pve_flutter_frontend 1/7] chore: ios: add SwiftPM support Shan Shaji
2026-10-30 12:06 ` [PATCH pve_flutter_frontend 2/7] chore: update Gradle, AGP and Kotlin versions Shan Shaji
2026-10-30 12:06 ` [PATCH pve_flutter_frontend 3/7] chore: add opt-out flags for built-in Kotlin and Gradle Kotlin DSL Shan Shaji
2026-10-30 12:06 ` [PATCH pve_flutter_frontend 4/7] chore: include non-Dart files to analyzers's exclude directive Shan Shaji
2026-10-30 12:06 ` [PATCH pve_flutter_frontend 5/7] chore: run `flutter pub upgrade` with flutter (v3.47) Shan Shaji
2026-10-30 12:06 ` [PATCH pve_flutter_frontend 6/7] chore: use caret syntax instead of any for shared_preferences plugin Shan Shaji
2026-10-30 12:06 ` [PATCH pve_flutter_frontend 7/7] chore: bump minimum supported OS version to 15 Shan Shaji
2026-10-30 12:06 ` [PATCH proxmox_login_manager 1/1] chore: run flutter pub upgrade Shan Shaji
2026-10-30 12:06 ` [PATCH proxmox_dart_api_client " Shan Shaji
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261030120617.56692-1-s.shaji@proxmox.com \
--to=s.shaji@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox