fix: correct version string for development builds

- Use git describe --exact-match to detect tagged commits
- Check for dirty working tree with git status --porcelain
- Use tag version ONLY if exact match AND clean working tree
- Otherwise fallback to v0.0.0-dev+<commit-hash> format
- Fixes issue where development builds showed old release tags

This ensures that:
1. Tagged commits with clean tree show release version (e.g., v1.0.0-beta.62)
2. Development builds show v0.0.0-dev+<commit-hash> format
3. Dirty working tree always shows dev version

Signed-off-by: NETIZEN-11 <niteshkumar121411@gmail.com>

Author: NETIZEN-11

Makefile

@@ -21,10 +21,23 @@ YEAR_GEN          := $(shell date '+%Y')
 
 GOBIN := $(shell go env GOPATH)/bin
 GIT_COMMIT := $(shell git rev-parse --short HEAD)
+GIT_TAG := $(shell git describe --tags --exact-match 2>/dev/null)
+DIRTY := $(shell git status --porcelain)
+
+# Version logic:
+# - Use tag ONLY if exact match AND clean working tree
+# - Otherwise fallback to dev version
+ifeq ($(GIT_TAG),)
+VERSION := v0.0.0-dev+$(GIT_COMMIT)
+else ifneq ($(DIRTY),)
+VERSION := v0.0.0-dev+$(GIT_COMMIT)
+else
+VERSION := $(GIT_TAG)
+endif
 
 export KPT_FN_WASM_RUNTIME ?= nodejs
 
-LDFLAGS := -ldflags "-X github.com/kptdev/kpt/run.version=${GIT_COMMIT}
+LDFLAGS := -ldflags "-X github.com/kptdev/kpt/run.version=${VERSION}
 ifeq ($(OS),Windows_NT)
 	# Do nothing
 else