v0.13.0

• After starting to support the multiversion CRDs in the providers, a new sync point is necessary for the import step because we scale up/down workloads and patch the objects. The new service endpoint-based sync point for workloads and retry mechanisms for patching operations were implented.
• Handle Namespace objects correctly during assertion steps (similar to K8s Secrets).

What's Changed

• Add a sync point for scaling up provider deployments by @sergenyalcin in #13
• Add one-pager about the switching to a new underlying test framework by @sergenyalcin in #11
• Add a endpoint based sync point after scaling up the pods in import step by @sergenyalcin in #14
• Add design-doc about the Uptest improvements by @sergenyalcin in #10
• Switch to crossplane/build by @negz in #16
• Handle Namespace v1 in the uptest run by @ytsarev in #19

New Contributors

• @negz made their first contribution in #16
• @ytsarev made their first contribution in #19

Full Changelog: v0.12.0...v0.13.0