prepare packages for semver

luyadev · Apr 1, 2019 · 7e53169 · 7e53169
1 parent 3a2dd99
commit 7e53169
Show file tree

Hide file tree

Showing 6 changed files with 10 additions and 10 deletions.
diff --git a/docs/guide/concept-core.md b/docs/guide/concept-core.md
@@ -36,7 +36,7 @@ The content for `composer.json` would be:
 ```json
 {
     "require": {
-        "luyadev/luya-core" : "~1.0.0"
+        "luyadev/luya-core" : "^1.0"
     },
     "config": {
         "fxp-asset" : {

diff --git a/docs/guide/install-structures.md b/docs/guide/install-structures.md
@@ -269,7 +269,7 @@ Create a composer.json
         }
     },
     "require-dev" : {
-        "luyadev/luya-core" : "~1.0.0"
+        "luyadev/luya-core" : "^1.0"
     },
     "extra" : {
         "luya" : {
@@ -288,7 +288,7 @@ Now you can include the private LUYA DI package into your projects:
 
 ```
 "require" : {
-    "mycompanyvendor/luya-di" : "~1.0.0",
+    "mycompanyvendor/luya-di" : "^1.0",
 },
 "repositories": [
     {

diff --git a/docs/guide/install-upgrade.md b/docs/guide/install-upgrade.md
@@ -11,9 +11,9 @@ Change the LUYA versions for each modules and LUYA itself in your composer.json
 
 ```json
 "require": {
-    "luyadev/luya-core" : "~1.0.0",
-    "luyadev/luya-module-cms" : "~1.0.0",
-    "luyadev/luya-module-admin" : "~1.2.0"
+    "luyadev/luya-core" : "^1.0",
+    "luyadev/luya-module-cms" : "^1.0",
+    "luyadev/luya-module-admin" : "^1.2"
 }
 ```
 

diff --git a/docs/guide/install-windows.md b/docs/guide/install-windows.md
@@ -13,7 +13,7 @@ composer global require "fxp/composer-asset-plugin:~1.4"
 After setting up Composer, we execute the Composer command `create-project` to checkout the **luya-kickstarter** application, an **out of the box** LUYA setup to run your website directly. It´s recommend to run the `create-project` command directly from your htdocs/webserver folder like this:
 
 ```sh
-composer create-project luyadev/luya-kickstarter:~1.0.0
+composer create-project luyadev/luya-kickstarter:^1.0
 ```
 
 > Note: During the installation Composer may ask for your Github login credentials. This is normal because Composer needs to get enough API rate-limit to retrieve the dependent package information from Github. For more details, please refer to the [Composer documentation](https://getcomposer.org/doc/articles/troubleshooting.md#api-rate-limit-and-oauth-tokens).

diff --git a/docs/guide/install.md b/docs/guide/install.md
@@ -13,7 +13,7 @@ composer global require "fxp/composer-asset-plugin:~1.4"
 After setting up Composer, we execute the Composer command `create-project` to checkout the **luya-kickstarter** application, an **out of the box** LUYA setup to run your website directly. It´s recommend to run the `create-project` command directly from your htdocs/webserver folder like this:
 
 ```sh
-composer create-project luyadev/luya-kickstarter:~1.0.0
+composer create-project luyadev/luya-kickstarter:^1.0
 ```
 
 > Note: During the installation Composer may ask for your Github login credentials. This is normal because Composer needs to get enough API rate-limit to retrieve the dependent package information from Github. For more details, please refer to the [Composer documentation](https://getcomposer.org/doc/articles/troubleshooting.md#api-rate-limit-and-oauth-tokens).

diff --git a/docs/guide/luya-package-dev.md b/docs/guide/luya-package-dev.md
@@ -26,7 +26,7 @@ cd luya-package-skeleton
     "name": "username/package",
     "type": "luya-extension",
     "require-dev": {
-        "luyadev/luya-testsuite": "~1.0.0"
+        "luyadev/luya-testsuite": "^1.0"
     },
     "autoload" : {
         "psr-4" : {
@@ -70,7 +70,7 @@ As LUYA is built upon the composer package manager every extension must be inclu
     "type": "luya-extension",
     "minimum-stability": "stable",
     "require": {
-        "luyadev/luya-core": "~1.0.0"
+        "luyadev/luya-core": "^1.0"
     },
     "extra": {