We unfortunately fall into the "3rd party construct" category, so I think we're still fragile.
This change does not completely solve the versioning issue yet,
as after this change customers and potential 3rd party construct
libraries they use still need to agree on the version of CDK to
be used (both need to use caret versioning, ensuring they always
get the latest version, or both need to use fixed versioning.
When version specifiers are mixed, multiple copies of the CDK will
be pulled into the dependency tree as soon as a ^caret version
can resolve to a new CDK release).
Updating to the latest version of dependencies to at least mitigate: https://github.com/punchcard/punchcard/issues/59
Related PR from the CDK team to help this situation: https://github.com/aws/aws-cdk/pull/4470
We unfortunately fall into the "3rd party construct" category, so I think we're still fragile.