Version handling for releases from GitHub

[RobjS]

Following the move to releasing on GitHub rather the WordPress directory, I was curious how version releases will work.

The instructions in the README say to install the latest version of the master branch:

https://github.com/billerickson/be-media-from-production/archive/master.zip --force --activate

However, unless every commit to master is marked as a new version (which hasn't been the case in the commit history to date), it seems like this could result in a number of commits could be marked as having the same version, i.e. one site's vX.Y won't necessarily be identical to another's, if they were installed at different times.

Could this be solved by e.g. using a latest tag which points to the commit for the latest formal release, so therefore should always be available from https://github.com/billerickson/be-media-from-production/archive/refs/tags/latest.zip? Then that tag could just be moved once a new release was ready. Historical releases could also be made available from https://github.com/billerickson/be-media-from-production/archive/refs/tags/[vX.Y].zip if they were also tagged with the appropriate version.