build: Implement semantic versioning in build system

[NETIZEN-11]

Description

This PR implements semantic versioning in the kpt build system using Git tags. It ensures that the version is correctly injected into the binary at build time and provides consistent version output across all architectures.

Part of #4450 - Stabilize kpt API to version 1

Changes Made

Makefile Updates

1. Semantic Version Detection

   • Uses git describe --tags --match='v*' to automatically detect version from Git tags
   • Follows semantic versioning format: vMAJOR.MINOR.PATCH
   • Fallback to v0.0.0-dev+{commit-hash} for development builds
   • Ensures version consistency across all build environments

2. Version Injection via ldflags

   • Injects version into github.com/kptdev/kpt/run.version variable
   • Version is embedded at compile time
   • Works seamlessly with the updated version command

How It Works

# Automatic version detection
VERSION := $(shell git describe --tags --match='v*' --abbrev=0 2>/dev/null || echo "v0.0.0-dev+${GIT_COMMIT}")

# Version injection during build
LDFLAGS := -ldflags "-X github.com/kptdev/kpt/run.version=${VERSION}"

[netlify]

✅ Deploy Preview for kptdocs ready!

Name	Link
🔨 Latest commit	805a22c
🔍 Latest deploy log	https://app.netlify.com/projects/kptdocs/deploys/69d55592ae77560009ba05ff
😎 Deploy Preview	https://deploy-preview-4468--kptdocs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Copilot]

Pull request overview

This PR implements semantic versioning in the kpt build system using Git tags. It detects versions from Git tags (matching the pattern v*) and injects them into the binary at build time. For development builds, it falls back to a dev version format with the commit hash. The PR also includes a major refactoring of the package update functionality with improved code structure and documentation, along with comprehensive render status tracking to capture detailed pipeline execution results.

Changes:

• Semantic version detection via git describe in Makefile with automatic fallback for dev builds
• Refactored PkgUpdate implementation with helper functions for better maintainability and clearer error handling
• Enhanced render status tracking throughout the pipeline execution to capture mutation and validation step results
• Cross-platform path handling improvements in Kptfile validation
• Updated Kubernetes dependencies to v0.35.0
• Updated krm-functions-catalog apply-setters from v0.2.2 to v0.2.4
• Build tag updates for wasmtime runtime support detection

Reviewed changes

Copilot reviewed 16 out of 17 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
Makefile	Added semantic version detection using git describe with GIT_COMMIT fallback
pkg/lib/kptops/pkgupdate.go	Refactored PkgUpdate into focused helper functions with improved documentation and error handling
pkg/api/kptfile/v1/validation.go	Fixed path validation to use path.IsAbs instead of filepath.IsAbs for cross-platform correctness
pkg/api/kptfile/v1/types.go	Added Resource field to ResultItem for render status tracking
internal/util/render/executor.go	Comprehensive render status tracking with pipeline step results and error aggregation
internal/util/render/executor_test.go	Updated tests with cross-platform path handling and render status verification; fixed mkdir bugs
internal/fnruntime/wasmtime.go	Updated build tags to exclude Windows from cgo-based wasmtime support
internal/fnruntime/wasmtime_unsupported.go	Updated build tags and fixed error message typos
internal/fnruntime/utils.go	Code style improvements (YAML string extraction)
internal/builtins/pkg_context.go	Improved path normalization and root package detection logic
internal/kptops/testdata/	Updated function version references from v0.2.0 to v0.2.4
go.mod	Updated Kubernetes and related dependencies to v0.35.0

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[CsatariGergely]

Please fix the DCO issue by following these instructions: https://github.com/kptdev/kpt/pull/4468/checks?check_run_id=70060980850

[NETIZEN-11]

@CsatariGergely Thanks for pointing this out. I've fixed the DCO issue and updated the commits. Kindly take another look.

[Copilot]

Pull request overview

Copilot reviewed 16 out of 17 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[aravindtga]

Hi @NETIZEN-11,

Thanks for your PR and contribution!

This currently has 23 commits, many of which are unrelated to the build versioning scope. They got included in your branch as part of a merge, This makes it hard to review what's actually part of your change.

Could you rebase cleanly onto main so only the semantic versioning changes are visible in the diff?

I'd also request the same for your other open PRs. That will make reviews much easier across the board and help get things merged faster.

Thanks!

[NETIZEN-11]

Hi @aravindtga,

Thanks for the feedback. I’ve rebased the branch onto main and cleaned up the commits. Now the PR only contains the relevant semantic versioning changes.

Could you please take another look?

Thanks!

I tested the solution and it does not seem to work correctly for development builds.

[liamfallon]

The solution here does not insert the correct version string into the binary when building a development version of kpt, see this log:

Before fix:

kpt % git status
On branch main
Your branch is up to date with 'origin/main'.

nothing to commit, working tree clean
kpt % make build
go build -ldflags "-X github.com/kptdev/kpt/run.version=2cd4e75fa " -o /Users/liam/go/bin/kpt -v .
github.com/kptdev/kpt
kpt % kpt version
2cd4e75fa

After fix:

kpt % git status
On branch main
Your branch is up to date with 'origin/main'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   Makefile

no changes added to commit (use "git add" and/or "git commit -a")
kpt % git diff
diff --git a/Makefile b/Makefile
index 7b64949f8..048641216 100644
--- a/Makefile
+++ b/Makefile
@@ -22,9 +22,12 @@ YEAR_GEN          := $(shell date '+%Y')
 GOBIN := $(shell go env GOPATH)/bin
 GIT_COMMIT := $(shell git rev-parse --short HEAD)
 
+# Use git describe to get semantic version, fallback to commit hash for dev builds
+VERSION := $(shell git describe --tags --match='v*' --abbrev=0 2>/dev/null || echo "v0.0.0-dev+${GIT_COMMIT}")
+
 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
kpt % make build
go build -ldflags "-X github.com/kptdev/kpt/run.version=v1.0.0-beta.62 " -o /Users/liam/go/bin/kpt -v .
github.com/kptdev/kpt
kpt % kpt version
v1.0.0-beta.62

I think the last version string should be v0.0.0-dev+2cd4e75fa

[NETIZEN-11]

@liamfallon Good catch, thanks for pointing this out!

You're right — the previous implementation was incorrectly picking the latest tag even for development builds.

I've updated the logic to:

• Use the tag only when the commit exactly matches a tag and the working tree is clean
• Fall back to v0.0.0-dev+<commit> for development/dirty builds

This should now produce the expected version string. Please take another look.

[Copilot]

Pull request overview

Copilot reviewed 16 out of 17 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.