Update all units to upstream v1.4.16

[manolobevia]

No description provided.

[jgreidy]

• Yesterday's upstream version, v1.4.15, did not have the latest version, tagged '2.1.1' of custom plugin GitHub "cul-it/wp-libcal-hours". When I built the upstream, I used 'composer update' instead of my usual process of deleting composer.lock and then running 'composer install'. Maybe I didn't save composer.json after editing it or something. I repeated the steps today and the correct version got in to composer.lock after the 'composer update'. So, we're using the 'v' prefix on version numbers as a convention, but if it's not there in the tag it should not matter. Just a coincidence that my error suggested the 'v' prefix was necessary.
• On the 'v' prefix of version numbers:
  • The semver.org spec says the v prefix is not correct: https://semver.org/#is-v123-a-semantic-version
  • GitHub uses the 'v' prefix as a convention to help distinguish version numbers from branches: https://github.com/marketplace/actions/git-semantic-version
  • Composer strips off the 'v' prefix: https://getcomposer.org/doc/articles/versions.md#tags
  • More about semantic versioning prefix conventions:
    • to v or not to v semver/semver#1
    • https://www.flownative.com/en/blog/semantic-versioning-and-different-version-number-formats.html

[manolobevia]

Note: I have deployed from dev to test and from test to live env with the wrong deploy comment. It should be release 1.4.16 instead of release 1.4.15. I forgot to change the deployment commit in the terminus script upstream update file.