Description of problem:

When updating `release.yaml` in the upstream Shipwright operator to use the v0.12.0 relese manifest, both unit and CI checks fail.

Prerequisites (if any, like setup, operators/versions):

• Shipwright operator upstream - current `main` branch.

Steps to Reproduce

1. Download the v0.12.0 release.yaml for the Shipwright Build controller
2. Replace kodata/release.yaml with the the v0.12.0 release.yaml
3. Submit a pull request/run unit and e2e CI tests

Actual results:

Unit tests fail in the integration/envtest phase.

e2e tests fail consistently

Expected results:

Unit and e2e tests should succeed, as this should be a no-op change.

Reproducibility (Always/Intermittent/Only Once):

Always

Acceptance criteria: 

release.yaml can be updated with the version downloadable from the GitHub release for Shipwright Build

Build Details:

Observed in pull request: https://github.com/shipwright-io/operator/pull/182

Additional info (Such as Logs, Screenshots, etc):

 
Upstream issue: https://github.com/shipwright-io/operator/issues/184

Approach

Use manifestival {{Transform}}s to truncate the "description" fields in our CRD manifests. Experimentation may be needed wrt how many characters we allow.