Address review comments

Author: pinkeshmars

docs/resources/projects/libraries.md

@@ -139,7 +139,7 @@ To import a library project into another FlutterFlow project, you must go to the
 - By default, the latest published version of the library is imported, but you can choose to depend on an earlier version if needed.
 - You can also import the `current` version of the library to use the latest state of the library on the main branch - however, this is not recommended.
 - You must have a paid plan to import a library.
-
+- When you import a library into a project or another library, the library’s version must be lower than the project or library it’s being imported into. Learn more about managing the library’s FlutterFlow version [**here**](version-management.md) and [**here**](version-management.md#version-management-with-libraries).
 :::
 
 
@@ -235,6 +235,8 @@ You can easily upgrade to newer versions of the libraries as they become availab
 
 ![update-library](imgs/update-library.avif)
 
+
+
 ## Library Values
 
 **Library values** are essentially variables created and used by a library author and intended to have their values set by the library user. These values allow library author to create configurable variables that are useful in different contexts, such as API keys, global settings, or other project-specific configurations. These values allow library users to input specific data required for the library to function properly in their project.

docs/resources/projects/version-management.md

@@ -14,9 +14,7 @@ FlutterFlow is constantly evolving to provide new features, address bugs, and ke
 To mitigate these issues, FlutterFlow offers you a **Version Management** system that allows you to pin your project to a particular stable release of FlutterFlow. Projects pinned to a stable release will **not** automatically receive the latest FlutterFlow updates, giving you more control and stability over your development environment.
 
 :::info
-
-The FlutterFlow Version Management feature is available only on [**paid plans**](https://www.flutterflow.io/pricing).
-
+Currently, the ability to pin a FlutterFlow project to a stable version is only available to **Enterprise** users.
 :::
 
 ## Why Version Management Matters
@@ -25,18 +23,23 @@ The FlutterFlow Version Management feature is available only on [**paid plans**]
 - **Offers Control Over Update Timing:** FlutterFlow updates might occur at inopportune times (e.g., right before you plan to deploy). Version Management allows you to choose **if and when** to move your project to a newer release.
 - **Enhances Reliability:** By using the pinned version, you can be confident that the same version of FlutterFlow, Flutter, and packages that you’ve tested will remain consistent, preventing surprises during critical development or deployment stages.
 
+:::warning
+That said, there are **downsides** to consider: pinning your project to a stable release means you won’t receive the newest FlutterFlow features or bug fixes as they’re released. **We only recommend doing this if you have complex app with dependencies or custom code that could break when upgraded.**
+:::
+
 ## Key Concepts
 
 Below are the foundational ideas behind FlutterFlow’s Version Management system. Understanding these concepts will help you maintain project stability and control when upgrading.
 
 ### Stable Release
 
-A **stable release** of FlutterFlow is a version that has passed rigorous testing and is frozen to specific:
+A **stable release** of FlutterFlow is a version that has passed careful testing and is frozen to a specific:
 
-- Flutter version
-- Pubspec dependencies
 - FlutterFlow frontend
 - Project code generation
+- Flutter version
+- Set of Pubspec dependencies
+
 
 Stable releases are chosen on a regular cadence (e.g., quarterly or monthly). **Note** that each stable release will be supported for a set duration (6 months by default).
 
@@ -45,20 +48,27 @@ Stable releases are chosen on a regular cadence (e.g., quarterly or monthly). **
 When you “pin” your project to a stable release, no updates from FlutterFlow will apply to your project during the pinned period. Each stable release will have associated web and desktop frontends, allowing you to continue working on your project without interruptions.
 
 :::info
-- **For Desktop**: You will download and install the dedicated binary for the pinned stable release. This binary won’t auto-update to give you a consistent development environment.
+- **For Desktop**: You will [**download**](https://www.flutterflow.io/desktop) and install the dedicated binary for the pinned stable release. This binary won’t auto-update to give you a consistent development environment.
 - **For Web**: You will access a unique URL to open the FlutterFlow pinned to that specific release.
 - **No forced upgrades**: You won’t be prompted to switch to the latest FlutterFlow release until your pinned version’s support window (e.g., 6 months) has ended.
+- **Pinning only from main branch**: You can only pin a FlutterFlow version if your project is on the main branch; pinning from other branches isn’t allowed.
 :::
 
-To pin a project, navigate to **Settings and Integrations > Project Setup > Pin Version** and select the stable release you want to lock into.
+### Viewing and Modifying Pinned Versions
 
-### Project Upgrades
+You can check the project’s pinned FlutterFlow version from the Dashboard.
 
-When your project is pinned, you can only upgrade to a later stable release (downgrading to a previous stable release is not allowed) once you decide to move on from the current pinned version. You can unpin your project at any time, which will automatically update it to the latest available FlutterFlow release.
+To change the pinned version, navigate to **Settings and Integrations > General > App Details >** scroll down to the **Version Pinning** section and select the stable release you want to lock into. Once you update the pinned version, you can only edit the project using that version of FlutterFlow.
 
-## FlutterFlow Version Workflow
+You can upgrade to a newer release or switch to an older one. However, if you choose to downgrade, any changes made after moving to a higher version will be lost.
+
+:::info
+**Note that** only project owners can modify the pinned version.
+:::
+
+
+## Recommended FlutterFlow Version Workflow
 
-Let’s understand the versioning workflow of setting up and managing a pinned project with an example. Understanding each phase ensures you can confidently control your project’s FlutterFlow version.
 
 ![versioning-workflow.avif](imgs/versioning-workflow.avif)
 
@@ -68,6 +78,16 @@ Let’s understand the versioning workflow of setting up and managing a pinned p
 4. **Upgrade Directly to the Next Stable Release**: When FlutterFlow designates a future stable release, you can jump straight from 4 to 4.5 or 5, bypassing any issues in the in-between versions. This way, you only upgrade once, reducing the risk of multiple compatibility checks along the way.
 5. **Stay in Control**: While pinned to a stable release, FlutterFlow will **not** automatically update your project. You alone decide when (and if) to move to a later stable release or whatever latest version by unpinning the project.
 
+## Version Management with Libraries
+
+[Libraries](libraries.md) have their own versions, and each library version corresponds to a specific FlutterFlow version. The FlutterFlow version of the library version is determined by the version used (pinned or otherwise) when the project was updated.
+
+Library projects can also be pinned to a specific version, ensuring that all library versions use that FlutterFlow release until the pinned version is changed.
+
+:::info
+When you import a library into a project or another library, the library’s version must be lower than the project or library it’s being imported into; otherwise, you will encounter an error.
+:::
+
 ## FAQs
 
 <details>
@@ -81,17 +101,37 @@ Any changes made in a higher version will be lost when you revert to a lower ver
 </details>
 
 <details>
-<summary>Can I downgrade my project after upgrading to a new stable release?</summary>
+<summary>
+Can I edit my project in multiple versions of FlutterFlow?
+</summary>
+<p>
+No. If your project is not pinned to a specific version, you’ll always use the latest FlutterFlow release. If your project is pinned to a specific version of FlutterFlow, you will be prompted to edit the project in that version.
+</p>
+</details>
+
+<details>
+<summary>
+How often are new stable versions released?
+</summary>
 <p>
-You will not be able to downgrade a project to a prior stable release. You can only choose to ‘pin’ your project to the next stable release that occurs (or has occurred) after your project change.
+We aim to release new stable versions of FlutterFlow once a month.
 </p>
 </details>
 
 <details>
 <summary>
-Can I open the same project in multiple versions of FlutterFlow simultaneously?
+How can I see what's included in a new stable version?
 </summary>
 <p>
-No, you cannot open the same project in two different versions of FlutterFlow at the same time.
+We’re currently working on displaying release notes directly in the product, so you can easily review what’s been added or changed in each new stable version.
 </p>
 </details>
+
+<details>
+<summary>
+What if there are bugs in the FlutterFlow version I’m using?
+</summary>
+<p>
+If critical bugs arise, we may provide hotfixes or patches for older FlutterFlow versions. However, some fixes depend on updating the underlying Flutter framework or related dependencies, which isn’t always feasible for older versions. This is a risk of staying on an older version of FlutterFlow as opposed to always using the latest.
+</p>
+</details>