Check if release number is newer than add tag reference with new release number

[bradleya]

Check if release number is newer than add tag reference with new release number

[BradleyA]

This test did not always change the release number in script.sh BUT when you look at the releases section on GitHub all the changes for script.sh are not always included. If the same release number is used as a previous release number the latest changes are not in the release section but the file does include the changes. If a new release number is used that is grader than the previous release number then all the changes are also included in the releases section on GitHub and the file does include the changes.
test file script.sh

#!/bin/bash
# 	script.sh  0.02.A.5  2018-07-22_19:37:05_CDT  https://github.com/BradleyA/test-markit.git   uadmin  three-rpi3b.cptx86.com 0.01  
# 	   test release number 0.02.A again out of order 

# 	script.sh  0.01.4  2018-07-22_19:33:27_CDT  https://github.com/BradleyA/test-markit.git  uadmin  three-rpi3b.cptx86.com 0.02.A  
# 	   test release number 0.01 when current release number is 0.02.A 

# 	script.sh  0.02.A.3  2018-07-22_19:30:32_CDT  https://github.com/BradleyA/test-markit.git  uadmin  three-rpi3b.cptx86.com 0.00-1-g5ca7151  
# 	   testing release number 0.02.A when current release number is 0.00 

# 	script.sh  0.00.2  2018-07-22_19:26:41_CDT  https://github.com/BradleyA/test-markit.git  uadmin  three-rpi3b.cptx86.com 0.00  
# 	   test release number 

# 	script.sh  0.00.1  2018-07-22_19:21:20_CDT  https://github.com/BradleyA/test-markit.git  uadmin  three-rpi3b.cptx86.com 'No-parent-git-tag-found-in-repository'  
# 	   test 0.00 release number 
###

[BradleyA]

Users may have a business case to git push a fix to a previous release while coding a later release in the same repository. Thus only display a WARNING and allow script to continue with git push.
Do not issue an ERROR and exit 1