Remove GIT_HASH from HELM_TAG to match release CLI lookup (#5188)

Author: rajeshvenkata

projects/tinkerbell/tinkerbell/Makefile

@@ -55,9 +55,9 @@ HELM_DESTINATION_REPOSITORY=tinkerbell/tinkerbell/tinkerbell-helm
 HELM_IMAGE_LIST=tinkerbell/tinkerbell/tinkerbell tinkerbell/tinkerbell/tink-agent
 
 # When GIT_TAG is a commit SHA (not semver), helm package requires a valid semver version.
-# Override HELM_TAG with a semver wrapper: 0.0.1-<commit>-<build-tooling-hash>
+# Override HELM_TAG with a semver wrapper: 0.0.1-<commit>
 # This must match the NonProdSourceImageTagFormat in eks-anywhere release CLI bundle_release.go
-HELM_TAG=0.0.1-$(GIT_TAG)-$(GIT_HASH)
+HELM_TAG=0.0.1-$(GIT_TAG)
 
 # Exclude from upgrade buildspec until migration is complete
 EXCLUDE_FROM_UPGRADE_BUILDSPEC=true

projects/tinkerbell/tinkerbell/README.md

@@ -40,3 +40,10 @@ Note: `secondstar` (SSH over serial) is excluded via patch as EKS-A does not use
 
 - Repository: https://github.com/tinkerbell/tinkerbell
 - The mono-repo consolidates: boots→smee, tink, rufio, hegel→tootles
+
+## GIT_TAG
+
+The `GIT_TAG` file uses a commit SHA from the upstream tinkerbell mono-repo. Since helm
+requires valid semver for chart versions, the Makefile overrides `HELM_TAG` with a `0.0.1-`
+prefix and the sedfile template uses `${HELM_TAG}` for the chart version. The release CLI
+in eks-anywhere uses a matching `"0.0.1-<gitTag>"` format for source image lookup.