Skip to content

fvm 3.0.0-beta.3

Pre-release
Pre-release
Compare
Choose a tag to compare
@github-actions github-actions released this 03 Oct 12:17
· 403 commits to main since this release
3.0.0-beta.3
d02bd71
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Added

  • Tighter VSCode integration, with configuration and settings management. FVM will now automatically configure VSCode to use the correct Flutter SDK version, triggering a termianl path update, so you can just use flutter, commands instead of fvm flutter
  • Git Flutter repository mirroring for faster cloning of new versions.
  • Added a check in .gitignore for the '.fvm' directory, and auto-adding it if necessary.
  • Added verification if cached Flutter SDK has been upgraded, and provide options for corrective actions.
  • Added a check for Flutter SDK constraints check for compatibility with current project.
  • Improved FVM configuration management and settings.
  • Ability to override FVM settings on a per project basis.
  • Windows "unpriviledge" mode. If you you choose to run fvm in unpriviledge mode, it will not require admin rights to run, however local Flutter SDK project references will be absolute paths instead of relative links.

Improvements

  • Much improved DX with better error messages and logging, and more helpful information and how to proceed.
  • Color output when using fvm flutter command proxy.
  • Better SDK switching workflow per project. Handle more edge cases, by doing SDK comparisons.
  • Better fvm doctor command. Now provides much better output and information about the project and environment.
  • Better Dart SDK environment support, minimizes conflicts between multiple environment Dart SDKs.
  • Improved fvm releases output.
  • Improved fvm list output.
  • Better error checking for fvm global command.
  • FVM update check now runs only once a day.
  • You can disable update check with the --update-check flag on fvm config

Changed

  • Command fvm releases now defaults to stable channel. Use --all flag to see all releases, or filter by channel.
  • Removed "flavor" command in favor for fvm use {flavor}
  • Removed "destroy" command in favor of fvm remove --all
  • Config file is now .fvmrc instead of .fvm/fvm_config.json, and .fvm can be added to .gitignore, FVM will migrate it automatically.
  • You can now use fvm use {version} --env {flavor} as an alias for flavor. Might be deprecated in the future since env has become a better description for environment specific settings than flavor.
  • When installing or using a Flutter repo commit hash, hash needs ot be 10 digits. FVM will now validate it, and provide the correct hash if it can.

Breaking Changes

  • Default FVM config location is now .fvmrc instead of .fvm/fvm_config.json. FVM will migrate it automatically. However .fvm should be ignored, if you depend on fvm_config.json in your tools or CI, you should update your configuration.
  • fvm install - Will not setup by default. Use --setup flag to setup Flutter SDK. Flag --skip-setup is removed.
  • fvm releases - Defaults to stable releases. Use --all flag to see all releases, or filter by channel using --channel {channel}.
  • fvm flavor - Removed in favor of fvm use {flavor}.
  • fvm use - Will always setup by default. Use --skip-setup flag to skip setup.
  • Environment variables FVM_HOME is now FVM_CACHE_PATH.
  • Environment variables FVM_GIT_CACHE is now FVM_FLUTTER_URL.

See the full changelog for changes in earlier releases.

Assets 10
Loading