FLUTTER ECOSYSTEM

btwld/fvm

Flutter バージョン管理：Flutter SDK バージョンを管理するためのシンプルな CLI。

GitHub で見る ↗

Stars: 5539
Forks: 283
最終プッシュ（UTC）: 2026/10/29
プロジェクト状態: 公開中

GITHUB Organization

Bitwild ↗

A Concepta innovation lab

United States of America

言語DartShellPythonPowerShellDockerfileRuby

技術トピック

# flutter # cli # dart # flutter-sdk-versions # flutter-releases # sdk # fvm

使用している依存関係

依存関係一覧 35 件

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
grinder開発用^0.9.5
test開発用^1.24.6
lints開発用^2.1.1
crypto開発用^3.0.3
http開発用^1.1.0
dart_code_metrics_presets開発用^2.9.0
build_runner開発用^2.4.8
dart_mappable_builder開発用^4.2.3
build_verify開発用^3.1.0
build_version開発用^2.1.1
mocktail開発用^1.0.4
husky開発用^0.1.7
lint_staged開発用^0.5.1

元の README

以下は英語原文のスナップショットです。最新版は GitHub をご覧ください。

README を開く / 閉じる

fvm

GitHub stars Pub Version Pub Likes Pub Points All Contributors MIT License Codecov Awesome Flutter

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.yml triggers 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 under tool/release_tool/ and requires Dart SDK >=3.8.0. CI pins this higher tool chain via the RELEASE_DART_SDK environment variable (currently 3.9.0) so it matches the versions packaged for Homebrew and other installers. If you run release tasks locally, switch to a Dart SDK 3.8.0 or newer before executing commands from tool/release_tool/.

Emergency Releases

For hotfixes or emergency releases:

Update version manually in pubspec.yaml
Use individual platform workflows via manual dispatch:
- deploy_homebrew.yml for Homebrew updates
- deploy_docker.yml for Docker deployment
- Individual platform deployments as needed

For complete emergency deployment, create a GitHub release as normal.

See Workflow Documentation for detailed information.

Contributors

https://contrib.rocks/image?repo=btwld/fvm

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.