Epic Goal

Engage with Shipwright upstream to cut next feature release - v0.14.0, or a future version of Shipwright that we deem acceptable.

Why is this important?

• Bring in latest features, such as BUILD-1150
• Default storage of v1beta1 API.

Scenarios

1. Customer upgrades
2. Security imprvements

Acceptance Criteria (Mandatory)

• Shipwright Build version v0.14.z is deployed
• CI - MUST be running successfully with tests automated
• Release Technical Enablement - only release note provided, otherwise point customers to upstream documentation.

Dependencies (internal and external)

1. Upstream Shipwright Build v0.14 release

Previous Work (Optional):

N/A

Open questions::

Technical enablement of new Shipwright features? Will come in builds-1.4.

Vulnerability scanning feature - communicated as "Developer Preview" (it is an opt-in feature per Build).

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment