Skip to content

Deprecation policy

Staying on a supported Flutter version and Shorebird CLI gets you the latest security and bug fixes. This page says how long each is supported and how you hear about a retirement before it affects you.

Apps already in the app stores keep running through a retirement, and keep downloading and installing the patches you’ve already published.

WhatSupported for at least
Flutter (Android and iOS)2 years from release
Shorebird CLI6 months from release

macOS, Windows and Linux have newer minimums. The current minimum Flutter version for each platform is in Supported Flutter versions. Once a Flutter version is retired, new releases on it are refused. Patching has its own minimums, listed on the same page: you can keep patching releases already built on a retired version on Android, and on iOS when the release was built with Flutter 3.22.2 or later, but on macOS, Windows and Linux a new patch needs the same minimum as a new release. Enterprise plans can include longer Flutter support.

Creating releases with an older Shorebird CLI

Section titled “Creating releases with an older Shorebird CLI”

A Shorebird CLI past its support window first loses the ability to create new apps and releases, including adding a platform to an existing release; that alone doesn’t stop it patching, previewing or logging in, though some patches need a newer CLI for other reasons, such as managed signing or a recent Flutter version. Later a version can be refused for every command that reaches Shorebird’s servers, as CLIs older than 1.6.87 are today. Each change is listed under Upcoming with its date before it takes effect.

  1. Announced: listed under Upcoming with its date, at least 30 days ahead for a Shorebird CLI and 6 months ahead for Flutter.
  2. Warning: where Shorebird can reach affected teams, such as the console and the output of recent Shorebird CLIs, it tells them what to change and by when. Check this page too.
  3. Enforced: the retired version is refused, with an error naming the fix.
  • On your machine: run shorebird upgrade; see Keeping Shorebird up to date.
  • In CI: install the latest Shorebird at the start of every job instead of pinning a Shorebird version, and pin your Flutter version with shorebird release --flutter-version. Setup Shorebird does the install on GitHub Actions; see Continuous Integration for other providers.

No retirements are scheduled.