Skip to content

Commit 43c05f0

Browse files
authored
Update version-management.md
fix typo
1 parent a72e2c6 commit 43c05f0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/resources/projects/settings/version-management.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ A **Stable Release** of FlutterFlow is released each time a new **Minor Version*
6262
- There has been significant changes to project code generation
6363
- There has been an update to the underlying Flutter or Pubspec dependency versions
6464

65-
Stable releases are usually deployed each month. A stable release will correspond with an underlying standard release (i.e. 1.0 corresponds to 1.0.1 in the above diagram).
65+
Stable releases are usually deployed each month. A stable release will correspond with an underlying standard release (i.e. 1.0 corresponds to 1.0.2 in the above diagram).
6666

6767
:::note
6868
Each stable release will be supported for **6 months** before you are forced to upgrade to the next stable version.
@@ -196,4 +196,4 @@ What is the recommended approach if I have multiple projects and libraries that
196196
<p>
197197
If you choose to pin your project to a stable version of FlutterFlow, we recommend pinning all your projects and dependencies to the same version - and trying to upgrade all projects to the next version around the same time. This makes it easier to ensure compatibilities between projects and libraries that depend on each other. Additionally, this makes it easier to have a single FlutterFlow desktop environment that you are working within.
198198
</p>
199-
</details>
199+
</details>

0 commit comments

Comments
 (0)