feat(codebuild): add support for macOS 15 runners

[ayush-panta]

Reason for this change

Although CodeBuild supports the macOS base:15 image (ref), the CDK does not support this.

Description of changes

I added an option for the BASE_15 image. This simply involved copying the logic for BASE_14 and changing 14 to 15.

Describe any new or updated permissions being added

NA.

Description of how you validated changes

I added unit and integration tests for the base:15 image following the example of the existing tests for the base:14 image.

Unit tests (aws-codebuild/test/project.test.ts) passed locally:

    ✓ has build image for Base 14 (32 ms)
    ✓ has build image for Base 15 (12 ms)
    ✓ can set macOS fleet with BASE_14 (11 ms)
    ✓ can set macOS fleet with BASE_15 (10 ms)
    ✓ can set imported macOS fleet with BASE_14 (11 ms)
    ✓ can set imported macOS fleet with BASE_15 (11 ms)

The integration tests (aws-codebuild/test/integ.project-macos-fleet-base{14/15}.js) were not as straightforward. In the CodeBuild stack logs in my console, the stacks were able to be created successfully but failed to delete. I believe this is expected with macOS fleets and for these test cases, especially as the base:14 test already existed in the codebase. I have included snapshots, as required.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

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

[aws-cdk-automation]

(This review is outdated)

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[ayush-panta]

Though the automated validation passes, I still have to add a snapshot for the base15 integration test.

Update: generated and added.

[ayush-panta]

Hello, just bumping this PR.

Pull request has been modified.

[ayush-panta]

Hi @ozelalisen, thank you for your suggestions. I've made the necessary changes.

[github-actions]

	Tests	Passed ☑️	Skipped	Failed ❌️
Security Guardian Results	104 ran	100 passed		4 failed

Test	Result
Security Guardian Results
packages/@aws-cdk-testing/framework-integ/test/aws-codebuild/test/integ.project-macos-fleet-base14.js.snapshot/MacOsProjectIntegTestDefaultTestDeployAssertB425ECC4.template.json
iam-no-wildcard-actions-inline.guard	❌ failure
packages/@aws-cdk-testing/framework-integ/test/aws-codebuild/test/integ.project-macos-fleet-base14.js.snapshot/aws-cdk-project-macos-base14.template.json
iam-no-wildcard-actions-inline.guard	❌ failure
packages/@aws-cdk-testing/framework-integ/test/aws-codebuild/test/integ.project-macos-fleet-base15.js.snapshot/MacOsProjectIntegTestDefaultTestDeployAssertB425ECC4.template.json
iam-no-wildcard-actions-inline.guard	❌ failure
packages/@aws-cdk-testing/framework-integ/test/aws-codebuild/test/integ.project-macos-fleet-base15.js.snapshot/aws-cdk-project-macos-base15.template.json
iam-no-wildcard-actions-inline.guard	❌ failure

• View Security Guardian Results

[github-actions]

	Tests	Passed ☑️	Skipped	Failed ❌️
Security Guardian Results with resolved templates	104 ran	100 passed		4 failed

Test	Result
Security Guardian Results with resolved templates
packages/@aws-cdk-testing/framework-integ/test/aws-codebuild/test/integ.project-macos-fleet-base14.js.snapshot/MacOsProjectIntegTestDefaultTestDeployAssertB425ECC4.template.json
iam-no-wildcard-actions-inline.guard	❌ failure
packages/@aws-cdk-testing/framework-integ/test/aws-codebuild/test/integ.project-macos-fleet-base14.js.snapshot/aws-cdk-project-macos-base14.template.json
iam-no-wildcard-actions-inline.guard	❌ failure
packages/@aws-cdk-testing/framework-integ/test/aws-codebuild/test/integ.project-macos-fleet-base15.js.snapshot/MacOsProjectIntegTestDefaultTestDeployAssertB425ECC4.template.json
iam-no-wildcard-actions-inline.guard	❌ failure
packages/@aws-cdk-testing/framework-integ/test/aws-codebuild/test/integ.project-macos-fleet-base15.js.snapshot/aws-cdk-project-macos-base15.template.json
iam-no-wildcard-actions-inline.guard	❌ failure

• View Security Guardian Results with resolved templates

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Merge Queue Status

🚫 The pull request has left the queue (rule: default-squash) at f1cae44

This pull request spent 4 seconds in the queue, with no time running CI.

Reason

The pull request can't be updated

For security reasons, Mergify can't update this pull request. Try updating locally.
GitHub response: refusing to allow a GitHub App to create or update workflow .github/workflows/issue-label-assign.yml without workflows permission

Hint

You should update or rebase your pull request manually. If you do, this pull request will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Merge Queue Status

✅ The pull request has been merged at 1f0a1d3

This pull request spent 5 hours 59 minutes 45 seconds in the queue, including 5 hours 59 minutes 35 seconds running CI.
The checks were run in-place.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • feat(codebuild): add support for macOS 15 runners #35836
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • feat(codebuild): add support for macOS 15 runners #35836
• any of [🛡 GitHub branch protection]:
  • check-success = validate-pr
  • check-neutral = validate-pr
  • check-skipped = validate-pr
• any of [🛡 GitHub branch protection]:
  • check-success = build
  • check-neutral = build
  • check-skipped = build

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.