more fixes + updated documentation

Author: arcuri82

.github/workflows/release.yml

@@ -66,7 +66,7 @@ jobs:
         uses: actions/upload-artifact@v3
         with:
           name: evomaster.msi
-          path: release/evomaster-${evomaster-version}.msi
+          path: release/evomaster-${{env.evomaster-version}}.msi
           retention-days: ${{env.retention-days}}
           if-no-files-found: error
 
@@ -91,7 +91,7 @@ jobs:
         uses: actions/upload-artifact@v3
         with:
           name: evomaster.dmg
-          path: release/evomaster-${evomaster-version}.dmg
+          path: release/evomaster-${{env.evomaster-version}}.dmg
           retention-days: ${{env.retention-days}}
           if-no-files-found: error
 
@@ -116,7 +116,7 @@ jobs:
         uses: actions/upload-artifact@v3
         with:
           name: evomaster.deb
-          path: release/evomaster-${evomaster-version}-1_amd64.deb
+          path: release/evomaster-${{env.evomaster-version}}-1_amd64.deb
           retention-days: ${{env.retention-days}}
           if-no-files-found: error
 
@@ -164,7 +164,7 @@ jobs:
           fail_on_unmatched_files: true
           files: |
             evomaster.jar
-            evomaster-${evomaster-version}.msi
-            evomaster-${evomaster-version}.dmg
-            evomaster-${evomaster-version}-1_amd64.deb
+            evomaster-${{env.evomaster-version}}.msi
+            evomaster-${{env.evomaster-version}}.dmg
+            evomaster-${{env.evomaster-version}}-1_amd64.deb
 

docs/release.md

@@ -83,41 +83,20 @@ However, it might take some hours before those are in sync with Maven Central,
 which you can check at [https://search.maven.org/](https://search.maven.org/).
 
 
-## NPM Release
+## GitHub Release
 
-After the version number has been updated with `version.py` script, need to make a release on NPM as well.
-From folder:
+Push the version changes in the `pom.xml` files on Git.
 
-`client-js/evomaster-client-js`
+Create a Git _tag_ in the form `v<version>`, e.g., `v0.4.0`, using the command:
 
-run the following commands:
 ```
-npm run build
-npm login
-npm publish
+git tag v<x.y.z>
+git push origin v<x.y.z>   
 ```
+This will trigger a special build on GitHub Action (see `.github/workflows/release.yml`).
+If everything goes correctly, then after that action is completed the new release should be available on the [release page](https://github.com/EMResearch/EvoMaster/releases).
 
-Note that login will ask for username/password.
-The release is linked to NPM's user `arcuri82`.
-Password is ???.
-
-## NuGet Release
-
-After the version number has been updated with `version.py` script, need to make a release on NuGet as well for the .NET libraries.
-
-First, build .NET libraries with:
-
-`dotnet build`
-
-Then, execute:
-
-`./client-dotnet/publish.sh ???` 
-
-It takes as input the API-KEY linked to the namespace `EvoMaster.*`.
-Note: API-KEYs only last 1 year, and then a new one needs to be created.
-
-
-## GitHub Release
+## GitHub Release (OLD MANUAL VERSION) 
 
 Push the version changes in the `pom.xml` files on Git.
 Build the whole `EvoMaster` from project root folder with:
@@ -196,4 +175,36 @@ This means:
 
 
 
+## (DEPRECATED) NPM Release
+
+After the version number has been updated with `version.py` script, need to make a release on NPM as well.
+From folder:
+
+`client-js/evomaster-client-js`
+
+run the following commands:
+```
+npm run build
+npm login
+npm publish
+```
+
+Note that login will ask for username/password.
+The release is linked to NPM's user `arcuri82`.
+Password is ???.
+
+## (DEPRECATED) NuGet Release
+
+After the version number has been updated with `version.py` script, need to make a release on NuGet as well for the .NET libraries.
+
+First, build .NET libraries with:
+
+`dotnet build`
+
+Then, execute:
+
+`./client-dotnet/publish.sh ???`
+
+It takes as input the API-KEY linked to the namespace `EvoMaster.*`.
+Note: API-KEYs only last 1 year, and then a new one needs to be created.