Of course the biolockj_controller image has to be updated with every major, minor and patch release.
But creating a new tag for each module with each minor release is needless.
Rather than using the method to get the current version as a tag, let most modules stagnate onto the current tag, and update with each major release, or about every ~~ 6 months.
The modules should still be set up with autobuilds, but just to tag them as "latest"; this is a way to check that as of the latest release the current dockerfile DID build. And when a module does need to be updated, we can just pull/tag/push the update from dockerhub.
Of course the biolockj_controller image has to be updated with every major, minor and patch release. But creating a new tag for each module with each minor release is needless. Rather than using the method to get the current version as a tag, let most modules stagnate onto the current tag, and update with each major release, or about every ~~ 6 months.
The modules should still be set up with autobuilds, but just to tag them as "latest"; this is a way to check that as of the latest release the current dockerfile DID build. And when a module does need to be updated, we can just pull/tag/push the update from dockerhub.