chore(codebuild): update default build image to STANDARD_4_0

[blimmer]

By default, CodeBuild projects were defaulting to aws/codebuild/standard:1.0, which is quite old. According to these docs:

The latest version of each image is cached. If you specify a more specific version, then CodeBuild provisions that version instead of the cached version. This can result in longer build times.

Before I specified a newer build image, my CodeBuild project was taking 4+ minutes to provision and I was confused about why it was so slow. When I dug deeper and found the docs linked above, provisioning took less than 30 seconds.

Therefore, to provide users the best out-of-the-box experience, I believe the default should be the newer, cached image. This PR updates that default.

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[gitpod-io]

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildProject6AEA49D1-qxepHUsryhcu
• Commit ID: 5b0e68e
• Result: FAILED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[blimmer]

I'll fix these tests up in a bit.

[skinny85]

Sorry, not before v2 😉

[blimmer]

Hey @skinny85 - I don't actually know about v2 - is there a code freeze or something?

[skinny85]

No, this would just be a breaking change in version 1.x of CDK. See #11960 .

[blimmer]

Ah, OK, I understand now. I didn't see that other issue. Are breaking changes only acceptable for certain (experimental) packages?

[skinny85]

Are breaking changes only acceptable for certain (experimental) packages?

Yep. When we declare a give package "Stable", like CodeBuild is now, we no longer allow breaking changes to it in minor releases (like 1.76.0 to 1.77.0).

Any breaking changes to these have to be reserved for a major version release (like 1.77.0 to 2.0.0).

[skinny85]

Closing in favor of #14472.