Update README.md

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.28
+ uses: MAD-I-T/magento-actions@v3.29
  env:
  COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
  with:
@@ -149,7 +149,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.28
+ uses: MAD-I-T/magento-actions@v3.29
  env:
  COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
  BUCKET_COMMIT: bucket-commit-${{github.sha}}.tar.gz
@@ -166,7 +166,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.28
+ uses: MAD-I-T/magento-actions@v3.29
  env:
  COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
  BUCKET_COMMIT: bucket-commit-${{github.sha}}.tar.gz
@@ -229,7 +229,7 @@ jobs:
  steps:
  - uses: actions/checkout@v4
  - name: 'install fresh magento and copy to repo'
- uses: MAD-I-T/magento-actions@v3.28
+ uses: MAD-I-T/magento-actions@v3.29
  env:
  COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
  with:
@@ -257,7 +257,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.28
+ uses: MAD-I-T/magento-actions@v3.29
  with:
  process: 'install-mage-os'
  magento_version: 2.4.5 #e.g: 2.4.0, 2.4.3, 2.4.4 nightly
@@ -281,7 +281,7 @@ jobs:
  steps:
  - uses: actions/checkout@v4
  - name: 'install fresh pwa studio code and copy to repo'
- uses: MAD-I-T/magento-actions@v3.28
+ uses: MAD-I-T/magento-actions@v3.29
  with:
  process: 'pwa-studio-install'
  #no_push: 1 //uncomment this to prevent files from getting pushed to repo
@@ -290,23 +290,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.28
+ uses: MAD-I-T/magento-actions@v3.29
  with:
  process: 'pwa-studio-install'
  #no_push: 1
  
  - name: 'launch magento2 build'
  if: (!cancelled())
  id: build
- uses: MAD-I-T/magento-actions@v3.28
+ uses: MAD-I-T/magento-actions@v3.29
  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.28
+ uses: MAD-I-T/magento-actions@v3.29
  env:
  BUCKET_COMMIT: bucket-commit-${{github.sha}}.tar.gz
  HOST_DEPLOY_PATH: ${{secrets.STAGE_HOST_DEPLOY_PATH}}
@@ -321,7 +321,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.28
+ uses: MAD-I-T/magento-actions@v3.29
  env:
  BUCKET_COMMIT: bucket-commit-${{github.sha}}.tar.gz
  HOST_DEPLOY_PATH: ${{secrets.STAGE_HOST_DEPLOY_PATH}}
@@ -349,7 +349,7 @@ For magento 2.4 and 2.3
 
 ```
 - name: 'test some specific module code quality'
- uses: MAD-I-T/magento-actions@v3.28
+ uses: MAD-I-T/magento-actions@v3.29
  env:
  COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
  with:
@@ -369,7 +369,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.28
+ uses: MAD-I-T/magento-actions@v3.29
  env:
  COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
  with:
@@ -406,7 +406,7 @@ For magento 2.4.x
 
 ```
 - name: 'This step will scan the files for security breach'
- uses: MAD-I-T/magento-actions@v3.28
+ uses: MAD-I-T/magento-actions@v3.29
  env:
  COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
  with:
@@ -422,7 +422,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.28
+ uses: MAD-I-T/magento-actions@v3.29
  env:
  COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
  with:
@@ -446,7 +446,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.28
+ uses: MAD-I-T/magento-actions@v3.29
  env:
  COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
  with:
@@ -456,7 +456,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.28
+ uses: MAD-I-T/magento-actions@v3.29
  env:
  COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
  with:
@@ -523,7 +523,7 @@ magento2-integration-test:
  steps:
  - uses: actions/checkout@v4
  - name: 'launch magento2 integration test'
- uses: MAD-I-T/magento-actions@v3.28
+ uses: MAD-I-T/magento-actions@v3.29
  env:
  COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
  with:
@@ -542,7 +542,7 @@ This feature utilizes the popular [bitExpert/phpstan-magento](https://github.com
 
 ```
  - name: 'phpstan analyzer'
- uses: MAD-I-T/magento-actions@v3.28
+ uses: MAD-I-T/magento-actions@v3.29
  with:
  process: 'phpstan'
  exec_path: 'vendor/magento/module-email/' # i.e when standalone third party module github repo ../Madit/Module
@@ -560,7 +560,7 @@ Mess detection on magento2 using github actions.
 
 ```
  - name: 'mess detector'
- uses: MAD-I-T/magento-actions@v3.28
+ uses: MAD-I-T/magento-actions@v3.29
  with:
  process: 'mess-detector'
  md_src_path: 'app/code/Madit/Sips2/'
@@ -575,7 +575,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.28
+ uses: MAD-I-T/magento-actions@v3.29
  env:
  COMPOSER_AUTH: ${{secrets.COMPOSER_AUTH}}
  with: