Awsx Breaking Change Evaluation

AWSX Breaking Change Evaluation

Use this skill to evaluate whether an AWSX change is compatibility-sensitive or

breaking for existing users.

This skill is for risk classification and required evidence. For component shape

guidance, use $awsx-component-design. For proof strategy, use

$awsx-test-authoring.

Rule Index

• rules/public-schema-surface.md: schema and generated SDK public-surface

changes.

• rules/code-vs-behavior-breaks.md: code-level breaks versus preview/update

behavior changes.

• rules/child-identity-and-aliases.md: child logical names, parentage, URNs,

aliases, and migration paths.

• rules/defaults-and-supporting-resources.md: defaults, default-created

resources, tags, and supporting-resource changes.

• rules/provider-region-behavior.md: provider and region propagation changes.
• rules/upstream-inherited-breaks.md: changes inherited from @pulumi/aws or

AWS behavior versus AWSX-added breakage.

How To Use

• Identify the user-visible surface touched by the change: schema, generated

SDKs, child resource identity, defaults, providers/regions, or preview/update

behavior.

• Read the matching rule file.
• Classify the change as clearly safe, compatibility-sensitive, or breaking.
• If compatibility-sensitive, require evidence: schema comparison, generated

diff, mock test, provider-upgrade preview, targeted acceptance test, or an

explicit maintainer decision.

• Check the upgrade scenarios that match the change: existing user code still

compiles, existing stack preview is stable, child resource identity remains

compatible, and new programs get the intended behavior.

• Report the classification and evidence. Do not smooth uncertainty into a

confident answer.

Stop Early

Stop before approving compatibility if:

• existing user code might need to change;
• existing stacks might preview replacements, creates, deletes, or changed

inputs after upgrade;

• child names, parentage, aliases, provider tokens, module paths, defaults, or

output presence changed;

• the only evidence is that TypeScript compiles;
• the change is inherited from upstream but AWSX may be adding extra behavior on

top.