NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
pub.dev, #3871 most downloaded on pub.dev
The lint rules used in developing Amplify Flutter packages and plugins.
Latest stable
3.1.6
Last release 4 months ago
21 Jul 2026
Release timing varies
gaps range from 3 weeks to 11 months
Nearly every release is documented
notes for 16 of 16 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
16 releases · first in 2021
Drag across the ruler to compare, or tap a release to open it.
Minor bug fixes and improvements
Minor bug fixes and improvements
chore(all): Bumped Dart SDK to ^3.9.0
Your coding agent can read these notes before it upgrades. Set up the MCP server →
chore(all): Bump Dart SDK to 3.8.0
chore(all): Bump Dart SDK to 3.7.0
Minor bug fixes and improvements
feat: update plus plugins version
Minor bug fixes and improvements
Minor bug fixes and improvements
chore(amplify_lints)!: Remove app_core.yaml and library_core.yaml
app_core.yaml and library_core.yaml^3.0.0)- Update repository URL
Enforce implementation_imports to align with package:lints
implementation_imports to align with package:lints- Fix package analysis issues
This release also addresses several bugs that required breaking changes to resolve. See the change log below for the full list of updates.
We are thrilled to release version 2.0 of the Amplify Flutter libraries to add support for Amplify Gen 2. Learn more about Amplify Gen 2 at https://docs.amplify.aws.
This release enables flexible storage paths when using Amplify Gen 2 Storage. This release also addresses several bugs that required breaking changes to resolve. See the change log below for the full list of updates.
If you are upgrading an existing project using Amplify Flutter v1 (created with Amplify Gen 1 CLI or a custom pipeline) please see the upgrade guide.
As always, you can find us on GitHub and Discord to answer any questions.
StoragePath (#4713)delimiter to S3ListPluginOptions (#4773)package:lints and package:flutter_lints dependencies to 2.0flutter_lib.yaml, dart.yaml -> library.yamlflutter_app.yaml -> app.yamlimplementation_imports lint for library.yaml and library_core.yamlIntroduced the following new lints to library.yaml:
always_use_package_importsavoid_classes_with_only_static_membersavoid_dynamic_callsavoid_field_initializers_in_const_classesavoid_js_rounded_intsavoid_multiple_declarations_per_linecascade_invocationscomment_referencesconditional_uri_does_not_existdeprecated_consistencyeol_at_end_of_fileflutter_style_todosjoin_return_with_assignmentno_runtimeType_toStringnoop_primitive_operationsomit_local_variable_typesprefer_asserts_in_initializer_listsprefer_final_in_for_eachprefer_final_localsprefer_if_elements_to_conditional_expressionsprefer_int_literalsprefer_null_aware_method_callsrequire_trailing_commassort_constructors_firsttighten_type_of_initializing_formalsunawaited_futuresunnecessary_null_checksuse_enumsuse_if_null_to_convert_nulls_to_boolsuse_late_for_private_fields_and_variablesuse_named_constantsuse_raw_stringsuse_setters_to_change_propertiesuse_string_buffersuse_super_parametersuse_test_throws_matchersuse_to_and_as_if_applicableIntroduced the following new lints to app.yaml:
avoid_dynamic_callsavoid_field_initializers_in_const_classeseol_at_end_of_fileflutter_style_todosomit_local_variable_typesprefer_final_in_for_eachprefer_final_localsprefer_int_literalsprefer_null_aware_method_callsrequire_trailing_commassecure_pubspec_urlssized_box_shrink_expandsort_constructors_firsttighten_type_of_initializing_formalsunawaited_futuresunnecessary_null_checksuse_colored_boxuse_decorated_boxuse_enumsuse_if_null_to_convert_nulls_to_boolsuse_late_for_private_fields_and_variablesuse_named_constantsuse_raw_stringsuse_setters_to_change_propertiesuse_super_parametersuse_test_throws_matchersTo allow migration to the new lints, the old lints are available as library_core.yaml and app_core.yaml with only the upgrade to package:lints and package:flutter_lints v2.0.
Dart 3 support (must update Dart SDK constraint to ^3.0.0)
^3.0.0)depend_on_referenced_packages and use_build_context_synchronously lintsWe are thrilled to release version 1.0 of the Amplify Flutter libraries!
We are thrilled to release version 1.0 of the Amplify Flutter libraries!
This release introduces a full rewrite of the Amplify libraries in Dart, allowing you to build AWS cloud-connected applications on every platform Flutter supports (iOS, Android, Web, macOS, Windows, and Linux).
If you've been using v0 in production, you can now safely migrate to v1. Check out our migration guide for more information.
UserAttributes field of a Pinpoint Endpoint by passing an AWSPinpointUserProfile to Amplify.Analytics.identifyUser.autoFlushEventsInterval in Analytics config can now be set in seconds to control how often cached events are auto-flushed. Beforehand, this value was inconsistently read as seconds on iOS and milliseconds on Android.GraphQLRequest now has an authorizationMode property so callers can specify the authorization mode directly.GraphQLRequest now has a headers property to specify HTTP headers.ModelSubscriptions) now support a where clause to use server-side subscription filters via model helpers.fetchAuthSession now supports a forceRefresh parameter which, when passed, will refresh User Pool tokens and AWS credentials regardless if they’ve expired.Amplify.Auth.signUp now provides the user ID of the created user. Previously this was only available after signing in.federateToIdentityPool API has been added to the Cognito plugin which allows federating directly into an Identity Pool to receive AWS credentials using a third-party identity provider (IdP) token.
Amplify.Auth.getPlugin(AmplifyAuthCognito.pluginKey) anytime after configuration.list API now supports pagination.uploadData and downloadData provide flexibility when dealing with data stored in memory.
uploadData supports uploading from various data formats such as raw bytes, JSON, strings, Data URLs, and more.getProperties allows retrieving S3 object metadata without downloading the object.copy, move, and removeMany APIs now support better control of your files.The following issues have been fixed in this release:
The following issues have been fixed in this release:
The following issues have been fixed in this release:
When interacting with GraphQL APIs, use the API category for all platforms or DataStore for iOS and Android. This is because we retained DataStore on the original Android & iOS implementation. We’re looking to bring data synchronization and offline data experiences to the web and desktop in the future and would love to get your feedback on this GitHub issue.
One column per quarter.