From 69c0fb45e4c0f46d541be099cda49baa3b9efaae Mon Sep 17 00:00:00 2001
From: WebVPF <61043464+WebVPF@users.noreply.github.com>
Date: Fri, 12 Jan 2024 05:02:42 +0200
Subject: [PATCH] Updated package versions for Development branch

https://wintercms.com/docs/v1.2/docs/setup/configuration#bleeding-edge-updates
---
 setup/configuration.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/setup/configuration.md b/setup/configuration.md
index 92eb9fa2..5001e9eb 100644
--- a/setup/configuration.md
+++ b/setup/configuration.md
@@ -206,11 +206,11 @@ You can instruct the platform to prefer test builds from the marketplace by chan
 > **TIP:** If you are using [Composer](../architecture/using-composer) to manage updates, you may replace the default Winter CMS requirements in your `composer.json` file with the following in order to download updates directly from the develop branch. This is more or less the same as enabling edge updates.
 
 ```json
-"winter/storm": "dev-develop as 1.0",
-"winter/wn-system-module": "dev-develop",
-"winter/wn-backend-module": "dev-develop",
-"winter/wn-cms-module": "dev-develop",
-"laravel/framework": "~6.0",
+"winter/storm": "dev-develop as 1.2.999",
+"winter/wn-system-module": "dev-develop as 1.2.999",
+"winter/wn-backend-module": "dev-develop as 1.2.999",
+"winter/wn-cms-module": "dev-develop as 1.2.999",
+"laravel/framework": "~9.0",
 ```
 
 ### Using a public folder