add a new feature/bug fix to branch, including revving SemVer versioninpackage.json
merge branch to master - this kicks off CI which publishes a new image to ECR
manually release a new version on GH which matches SemVer version in package.json
This has a few draw backs:
Automation in step 3 to push a new image above doesn't detect if SemVer has been incremented, this will always publish an image, overwriting an existing image in ECR with a new version of the image re-using the existing version value.
If you forget to do step 4 above, then the GH release version will be different than ECR
Suggestions to fix this Improve CI to:
Check for existing SemVer in ECR and not push a new image if version already exists (also don't cut a new GH version per next item).
Automatically create a new GH release when there's a new ECR release to ensure they're always in sync
Right now the process to do a new release is:
version
inpackage.json
version
inpackage.json
This has a few draw backs:
version
value.Suggestions to fix this Improve CI to: