feat(core): introducing CDK Mixins

[mrgrain]

Reason for this change

Mixins enable composable, reusable functionality that attaches to constructs without inheritance. A mixin author implements supports() and applyTo(), and consumers apply mixins to any scope using Mixins.of(scope).apply(myMixin). Construct selectors narrow the target set by resource type, path pattern, or ID glob. This composability is the key differentiator from Aspects: where Aspects visit every node in the tree, Mixins give authors fine-grained control over which constructs receive which behavior.

Description of changes

The core Mixins types (Mixins, Mixin, IMixin, MixinApplicator, ConstructSelector, and related interfaces) now live in @aws-cdk-lib/core/lib. The MIXIN_SYMBOL identifier changes from the preview value to @aws-cdk/core.Mixin, which deliberately breaks cross-version compatibility checks so that preview mixins and GA mixins remain distinct.

The @aws-cdk/mixins-preview package re-exports these types from aws-cdk-lib/core instead of bundling its own copies. Existing code that imports from @aws-cdk/mixins-preview continues to work without changes. The preview package keeps its additional features like built-in mixins and EventBridge event patterns.

A new "Mixins" section in the aws-cdk-lib README documents the Mixins.of() entry point, custom mixin creation, construct selection, and error handling with requireAny() / requireAll(). It sits right before the existing "Aspects" section because the two features are conceptually related.

Analytics metadata tracks mixin usage via aws:cdk:analytics:mixin node metadata. The FQN of first-party mixins (those with allowed package prefixes) is recorded; third-party or unidentified mixins are redacted to *.

Describe any new or updated permissions being added

N/A

Description of how you validated changes

aws-cdk-lib compiles cleanly with tsc --noEmit. Unit tests cover the Mixin base class, MixinApplicator (including requireAny/requireAll semantics and ordering guarantees), ConstructSelector variants, and metadata recording with FQN redaction.

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.

[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

Rule: priority-squash

---

• ✅ Entered queue — 2026-02-27 11:41 UTC
• ✅ Checks passed · in-place
• ✅ Merged — 2026-02-27 11:41 UTC · at d8b76c68adf73974ba9643cbb1215d6060cddd7e

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

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • feat(core): introducing CDK Mixins #37055
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • feat(core): introducing CDK Mixins #37055
• 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

[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.