Instead of specifying the version range like "^2.0.0", the internal packages are pinned to specific versions.
supabase-js started doing this recently as well. With this, we can now the versions of the sub-libraries just by obtaining the supabase-flutter version, and it also helps with preventing accidental breaking change affecting a wider range if there were to be one.
What kind of change does this PR introduce?
Instead of specifying the version range like
"^2.0.0"
, the internal packages are pinned to specific versions.supabase-js started doing this recently as well. With this, we can now the versions of the sub-libraries just by obtaining the supabase-flutter version, and it also helps with preventing accidental breaking change affecting a wider range if there were to be one.