Shipwright Build release v0.16.0

Release changes since v0.15.0

Features

#1890 by @ayushsatyam146: The source.git.depth Was added to the Build resource to specify the depth of the Git history. If not specified the default value is 1 which means that no history is cloned at all. This is the fastest way to clone a Git repository and in most cases enough as long as you don't have anything in your build logic relying on it. Any value greater than 1 will create a clone with the specified depth. For a full git history clone, depth must be set to 0. Note: If you specify a commit sha as revision, then the full history is always cloned before this commit is checked out.

#1869 by @SaschaSchwarze0: Improve resource consumption by only caching shipwright-related taskruns and pods

Fixes

#1905 by @Bryce-huang: TaskRuns that timed out without a timeout in their spec do not anymore cause the controller to panic

#1880 by @SaschaSchwarze0: When specifying a Git source with a revision value which is a full commit SHA, then the source step now clones the repository at that point with the provided depth (default 1). Previously, when the revision was a commit SHA, it has always cloned the full history. This continues to be the case when you provide a short commit SHA. Note that this new approach is only used if Git supports the revision flag on git clone. This is not the case with the ubi9-based images that Shipwright provides.

API Changes

#1890 by @ayushsatyam146: The source.git.depth Was added to the Build resource to specify the depth of the Git history. If not specified the default value is 1 which means that no history is cloned at all. This is the fastest way to clone a Git repository and in most cases enough as long as you don't have anything in your build logic relying on it. Any value greater than 1 will create a clone with the specified depth. For a full git history clone, depth must be set to 0. Note: If you specify a commit sha as revision, then the full history is always cloned before this commit is checked out.

Docs

Misc

#1879 by @SaschaSchwarze0: Shipwright Build now requires at least Kubernetes v1.30 and Tekton v0.62

#1838 by @shipwright-ci-bot: Update the the new latest Tekton LTS release v0.68.1

#1823 by @SaschaSchwarze0: The role bindings related to the multiarch-native-buildah cluster build strategy sample are now not anymore included in our sample-strategies.yaml file. You must manually apply them to the namespaces where you plan to use this strategy.