Update README.md to match current release v3.30

MAD-I-T · Jul 31, 2024 · d851c34 · d851c34
1 parent 7e5886a
commit d851c34
Showing 1 changed file with 21 additions and 21 deletions.
diff --git a/README.md b/README.md
@@ -58,7 +58,7 @@ Config sample when using magento v2.4.X
      - uses: actions/checkout@v4
      - name: 'this step will build an magento artifact'
        if: (!cancelled())
-       uses: MAD-I-T/magento-actions@v3.29
+       uses: MAD-I-T/magento-actions@v3.30
        env:
          COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
        with:
@@ -97,7 +97,7 @@ jobs:
 
 To use the latest experimental version of the module set the following : (`uses: MAD-I-T/magento-actions@master`)
 
-If some issues are encountered on 2.3.X version, please use the **v2.0** of the action in place of **v3.28** 
+If some issues are encountered on 2.3.X version, please use the **v2.0** of the action in place of **v3.30** 
 
 Also, in some custom cases it may be needed to force/specify the php version to use in the step. 
 This can be done by adding php input (after **with:** option).
@@ -150,7 +150,7 @@ For magento 2.4 & 2.3
 
 ```
 - name: 'this step will deploy your build to deployment server - zero downtime'
-  uses: MAD-I-T/magento-actions@v3.29
+  uses: MAD-I-T/magento-actions@v3.30
   env:
     COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
     BUCKET_COMMIT: bucket-commit-${{github.sha}}.tar.gz
@@ -167,7 +167,7 @@ For magento 2.4 & 2.3
 
 - name: 'unlock php deployer if the deployment fails'
   if: failure() || cancelled()
-  uses: MAD-I-T/magento-actions@v3.29
+  uses: MAD-I-T/magento-actions@v3.30
   env:
     COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
     BUCKET_COMMIT: bucket-commit-${{github.sha}}.tar.gz
@@ -230,7 +230,7 @@ jobs:
     steps:
     - uses: actions/checkout@v4
     - name: 'install fresh magento and copy to repo'
-      uses: MAD-I-T/magento-actions@v3.29
+      uses: MAD-I-T/magento-actions@v3.30
       env:
         COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
       with:
@@ -258,7 +258,7 @@ One can also download magento code source from the [mage-os](https://mage-os.org
 See [this repository](https://github.com/seyuf/mage-os-actions.git).
 ```
     - name: 'install fresh magento from mage-os'
-      uses: MAD-I-T/magento-actions@v3.29
+      uses: MAD-I-T/magento-actions@v3.30
       with:
         process: 'install-mage-os'
         magento_version: 2.4.5  #e.g: 2.4.0, 2.4.3, 2.4.4 nightly
@@ -282,7 +282,7 @@ jobs:
     steps:
     - uses: actions/checkout@v4
     - name: 'install fresh  pwa studio code and copy to repo'
-      uses: MAD-I-T/magento-actions@v3.29
+      uses: MAD-I-T/magento-actions@v3.30
       with:
         process: 'pwa-studio-install'
         #no_push: 1 //uncomment this to prevent files from getting pushed to repo
@@ -291,23 +291,23 @@ jobs:
 One can also **install and deploy** a standalone PWA-studio website see the video below:
 ```
       - name: 'install fresh pwa-studio project'
-        uses: MAD-I-T/magento-actions@v3.29
+        uses: MAD-I-T/magento-actions@v3.30
         with:
           process: 'pwa-studio-install'
           #no_push: 1
           
       - name: 'launch magento2 build'
         if: (!cancelled())
         id: build
-        uses: MAD-I-T/magento-actions@v3.29
+        uses: MAD-I-T/magento-actions@v3.30
         env:
           COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
         with:
           process: 'build'
           
       - name: 'launch magento2 zero downtime deploy'
         if: (steps.build.outcome == 'success') && (!cancelled())
-        uses: MAD-I-T/magento-actions@v3.29
+        uses: MAD-I-T/magento-actions@v3.30
         env:
           BUCKET_COMMIT: bucket-commit-${{github.sha}}.tar.gz
           HOST_DEPLOY_PATH: ${{secrets.STAGE_HOST_DEPLOY_PATH}}
@@ -322,7 +322,7 @@ One can also **install and deploy** a standalone PWA-studio website see the vide
       - name: 'unlock deployer if failure'
         if: ${{false}}
         #if: failure()
-        uses: MAD-I-T/magento-actions@v3.29
+        uses: MAD-I-T/magento-actions@v3.30
         env:
           BUCKET_COMMIT: bucket-commit-${{github.sha}}.tar.gz
           HOST_DEPLOY_PATH: ${{secrets.STAGE_HOST_DEPLOY_PATH}}
@@ -350,7 +350,7 @@ For magento 2.4 and 2.3
 
 ```
 - name: 'test some specific module code quality'
-  uses: MAD-I-T/magento-actions@v3.29
+  uses: MAD-I-T/magento-actions@v3.30
   env:
     COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
   with:
@@ -370,7 +370,7 @@ For magento 2.4.x (**remove elasticsearch: 1 when building with 2.3.X**)
 
 ```
 - name: 'This step will build an magento artifact'
-  uses: MAD-I-T/magento-actions@v3.29
+  uses: MAD-I-T/magento-actions@v3.30
   env:
     COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
   with:
@@ -407,7 +407,7 @@ For magento 2.4.x
 
 ```
 - name: 'This step will scan the files for security breach'
-  uses: MAD-I-T/magento-actions@v3.29
+  uses: MAD-I-T/magento-actions@v3.30
   env:
     COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
   with:
@@ -423,7 +423,7 @@ For magento 2.4.x
 ```
 - name: 'This step will check all modules for security vulnerabilities'
     if: (steps.build.outcome == 'success') && (!cancelled())
-    uses: MAD-I-T/magento-actions@v3.29
+    uses: MAD-I-T/magento-actions@v3.30
     env:
       COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
     with:
@@ -447,7 +447,7 @@ See code sample to unit test your custom or a thrid party magento2 module [here]
 For magento 2.4.x  
 ```
 - name: 'This step will execute all the unit tests available'
-  uses: MAD-I-T/magento-actions@v3.29
+  uses: MAD-I-T/magento-actions@v3.30
   env:
     COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
   with:
@@ -457,7 +457,7 @@ For magento 2.4.x
 Run all unit test of the magento email module
 ```
 - name: 'This step will execute specific unit tests in the path dir'
-  uses: MAD-I-T/magento-actions@v3.29
+  uses: MAD-I-T/magento-actions@v3.30
   env:
     COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
   with:
@@ -524,7 +524,7 @@ magento2-integration-test:
   steps:
     - uses: actions/checkout@v4
     - name: 'launch magento2 integration test'
-      uses: MAD-I-T/magento-actions@v3.29
+      uses: MAD-I-T/magento-actions@v3.30
       env:
         COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
       with:
@@ -543,7 +543,7 @@ This feature utilizes the popular [bitExpert/phpstan-magento](https://github.com
 
 ```
   - name: 'phpstan analyzer'
-    uses: MAD-I-T/magento-actions@v3.29
+    uses: MAD-I-T/magento-actions@v3.30
     with:
       process: 'phpstan'
       exec_path: 'vendor/magento/module-email/' # i.e when standalone third party module github repo ../Madit/Module
@@ -561,7 +561,7 @@ Mess detection on magento2 using github actions.
 
 ```
   - name: 'mess detector'
-    uses: MAD-I-T/magento-actions@v3.29
+    uses: MAD-I-T/magento-actions@v3.30
     with:
       process: 'mess-detector'
       md_src_path: 'app/code/Madit/Sips2/'
@@ -576,7 +576,7 @@ Also see standalone third party module use case [here](https://github.com/MAD-I-
 For magento 2.3 & 2.4 
 ```
 - name: 'This step starts static testing the code'
-  uses: MAD-I-T/magento-actions@v3.29
+  uses: MAD-I-T/magento-actions@v3.30
   env:
     COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
   with: