Changes proposed in this pull request
Currently, protocol-common will try to deploy on any change merged to main, but it takes the version from package.json. The problem here is that there might not be any changes to the version in package.json, or it might be that we want to release only after a few changes have been made. Therefore, this change is to deploy only if the package.json version has been updated and is different from the one deployed in the npm registry.
🚀 Deployment changes 🚀
(list added or removed env, db changes etc)
(Click here if you don't understand these emojis)
What issue is this targeting?
Changes proposed in this pull request Currently, protocol-common will try to deploy on any change merged to main, but it takes the version from package.json. The problem here is that there might not be any changes to the version in package.json, or it might be that we want to release only after a few changes have been made. Therefore, this change is to deploy only if the package.json version has been updated and is different from the one deployed in the npm registry.
🚀 Deployment changes 🚀
(list added or removed env, db changes etc)
Other Notes
Signed-off-by: Jeff Kennedy jeffk@kiva.org