Make changes related to release and deploy

[PradeepWeb77]

Make changes related to release and deploy

[julianidiart]

For semantic release to work, you must follow the specifications for commit messages, check here: https://www.conventionalcommits.org/en/v1.0.0/#summary. Otherwise, semantic release will not create a new tag.

[julianidiart]

@PradeepWeb77, check this comment:

For semantic release to work, you must follow the specifications for commit messages, check here: https://www.conventionalcommits.org/en/v1.0.0/#summary. Otherwise, semantic release will not create a new tag.

You're still committing with a non-conventional commit message, which will result in the semantic release not being triggered once we merge with master branch.

Another thing I found with the last commit: If we rearrange the order of the steps, and get the last tag from GitHub before modifying the WordPress files, we don't need to look for the tag in version.sh and changelog.sh, we can pass it as an argument of the script and we avoid the same call 3 times.

Lastly, make sure you merge the latest changes from master, since there are some changes there, and there's a conflict with one file (package.json, it's related to the manual release of a new version).