fvm
Flutter-Versionen verwalten: Ein einfaches CLI zum Verwalten von Flutter SDK-Versionen.
- Sterne
- 5539
- Forks
- 283
- Letzter Push (UTC)
- 29.10.2026
- Projektstatus
- Aktiv
Original-README
Englischer Projektschnappschuss. Aktuelle Inhalte auf GitHub.
fvm
FVM manages Flutter SDK versions per project. Switch between Flutter versions instantly without reinstalling, making it easy to test new releases and maintain consistent builds across your team.
Why FVM?
- Need for simultaneous use of multiple Flutter SDKs.
- SDK testing requires constant channel switching.
- Channel switches are slow and need repeated reinstalls.
- Difficulty managing the latest successful SDK version used in an app.
- Flutter's major updates demand total app migration.
- Inconsistencies occur in development environments within teams.
For more information, read the Getting Started guide.
Release Process (For Maintainers)
FVM uses GitHub releases to trigger automated deployments across all platforms:
Creating a New Release
-
Ensure main branch is ready
- All changes merged and tested
- Version will be set automatically from release tag
-
Create GitHub Release
- Go to GitHub Releases
- Click "Create a new release"
- Choose tag:
v4.0.0-beta.2(follows semver with 'v' prefix) - Write release notes in GitHub editor
- Click "Publish release"
-
Automated Deployment
release.ymltriggers automatically- Deploys to: pub.dev, GitHub binaries, Homebrew, Chocolatey, Docker
- Monitor progress in Actions tab
Dart SDK requirements: Day-to-day development now targets the repository SDK constraint (
>=3.6.0 <4.0.0). Release automation lives undertool/release_tool/and requires Dart SDK>=3.8.0. CI pins this higher tool chain via theRELEASE_DART_SDKenvironment variable (currently3.9.0) so it matches the versions packaged for Homebrew and other installers. If you run release tasks locally, switch to a Dart SDK3.8.0or newer before executing commands fromtool/release_tool/.
Emergency Releases
For hotfixes or emergency releases:
- Update version manually in
pubspec.yaml - Use individual platform workflows via manual dispatch:
deploy_homebrew.ymlfor Homebrew updatesdeploy_docker.ymlfor Docker deployment- Individual platform deployments as needed
For complete emergency deployment, create a GitHub release as normal.
See Workflow Documentation for detailed information.
Contributors
Checkout Flutter Sidekick. Read more about it here.
Troubleshooting
Please view our FAQ.
License
This project is licensed under the MIT License; see LICENSE file for details.
Kategorien
Verwendete Abhängigkeiten
Abhängigkeiten 35 Einträge
- args
^2.4.2 - date_format
^2.0.7 - git
^2.2.1 - interact
^2.2.0 - io
^1.0.4 - mason_logger
^0.2.9 - meta
^1.10.0 - path
^1.9.0 - pub_semver
^2.1.4 - pub_updater
>=0.4.0 <0.6.0 - scope
^5.1.0 - yaml
^3.1.2 - yaml_edit
^2.2.0 - dart_console
^1.2.0 - tint
^2.0.1 - stack_trace
^1.11.1 - pubspec_parse
^1.5.0 - jsonc
^0.0.3 - dart_mappable
^4.2.2 - cli_completion
^0.5.0 - yaml_writer
^2.1.0 - win32
^5.0.0 - grinderEntwicklung
^0.9.5 - testEntwicklung
^1.24.6 - lintsEntwicklung
^2.1.1 - cryptoEntwicklung
^3.0.3 - httpEntwicklung
^1.1.0 - dart_code_metrics_presetsEntwicklung
^2.9.0 - build_runnerEntwicklung
^2.4.8 - dart_mappable_builderEntwicklung
^4.2.3 - build_verifyEntwicklung
^3.1.0 - build_versionEntwicklung
^2.1.1 - mocktailEntwicklung
^1.0.4 - huskyEntwicklung
^0.1.7 - lint_stagedEntwicklung
^0.5.1
Ranglisten
Wie wähle ich ein passendes Repository?
Nach Anwendungsfall filtern, Aktivität vergleichen und vor der Nutzung das Originalprojekt prüfen.
- Nach Name, Autor oder Beschreibung suchen und nach Thema eingrenzen.
- Sterne, Forks und letzte Pushes vergleichen. Sterne zeigen Interesse, garantieren aber keine Qualität.
- Vor der Nutzung README, Lizenz und Issues auf GitHub prüfen.
Quellen und Pflege
“A repository is the most basic element of GitHub.”
GitHub Docs — About repositories ↗
- btwld/fvm · GitHub ↗
- GitHub Docs — Saving repositories with stars ↗
- Verzeichnis gepflegt von Ducafecat ↗