Skip to content

Commit b80b88e

Browse files
committed
Add notice for project versions and commits
1 parent f1cc2d2 commit b80b88e

File tree

2 files changed

+5
-1
lines changed

2 files changed

+5
-1
lines changed

docs/testing-deployment-publishing/branching-collaboration/branching.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Branching creates a separate copy of your work, so you can add new features with
1414
Suppose you have an eCommerce app and you want to add a new feature, such as a product recommendation system. Instead of incorporating it directly into your `main` branch and potentially causing problems, you can create a branch to work on this new feature in isolation. Once it's complete, you can integrate it back into the `main` branch.
1515

1616
:::info
17-
This feature is only available for Pro, Teams and Enterprise users.
17+
While all users can access the branching menu and create commits, only **Pro**, **Teams**, and **Enterprise** plans support creating new branches.
1818
:::
1919

2020

docs/testing-deployment-publishing/branching-collaboration/saving-versioning.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,10 @@ In this section, we discuss the important concepts of saving and versioning in y
1313

1414
## Versions
1515

16+
:::warning[Project Versions are now deprecated]
17+
You can no longer create new versions in FlutterFlow. However, any previously created versions will remain accessible. Moving forward, we recommend using [**Commits**](#commits), which provides a more robust way to track changes and manage your project history.
18+
:::
19+
1620
Versions enable you to save specific named states of your project. This function is particularly useful for recovery purposes. If you accidentally delete a page or component or change settings, you can easily revert to a saved version.
1721

1822
### Saving a version

0 commit comments

Comments
 (0)