Browse Source

docs(docs): document versioning in app package

Signed-off-by: Nikolas Rimikis <leptopoda@users.noreply.github.com>
pull/1018/head
Nikolas Rimikis 1 year ago
parent
commit
776f48aef2
No known key found for this signature in database
GPG Key ID: 85ED1DE9786A4FF2
  1. 1
      docs/dependencies.md

1
docs/dependencies.md

@ -5,3 +5,4 @@ We follow the guidelines outlined in https://dart.dev/tools/pub/dependencies wit
2. Dev dependencies should be pinned to the latest versions since they do not affect consumers of our packages. 2. Dev dependencies should be pinned to the latest versions since they do not affect consumers of our packages.
3. Using Renovate we automatically update our dependency constraints. For non-dev dependencies this will be the latest major version, for everything else it will upgrade to the latest minor and patch versions as well. The lock files are also kept up-to-date with Renovate to compile everything with the latest available versions. 3. Using Renovate we automatically update our dependency constraints. For non-dev dependencies this will be the latest major version, for everything else it will upgrade to the latest minor and patch versions as well. The lock files are also kept up-to-date with Renovate to compile everything with the latest available versions.
4. The same rules and automatic workflows apply to the Dart and Flutter versions we use. 4. The same rules and automatic workflows apply to the Dart and Flutter versions we use.
5. The `app` package does not constrain the versions so the latest versions can be used.

Loading…
Cancel
Save