Tracking: [Library] Deployment Failure Due to Typeguard Version Update

Eva9260 commented 5 days ago

Overview

We encountered a deployment failure during our recent deployment caused by an unexpected version change in the typeguard library. Previously, we were using the following set of libraries:

aws-cdk-lib==2.161.1
aws-cdk.aws_scheduler_alpha==2.161.1a0
aws-cdk.aws_scheduler_targets_alpha==2.161.1a0
aws_cdk.aws_glue_alpha==2.161.1a0
aws_cdk.aws_lambda_python_alpha==2.161.1a0
constructs
yamldataclassconfig
yjrtr

This configuration worked fine in previous deployments. However, in the latest deployment, the typeguard version was unexpectedly updated to 4.3.0, causing the following error:

typeguard.TypeCheckError: list did not match any element in the union:
  Sequence[aws_cdk.aws_iam.IManagedPolicy]: item 0 is not compatible with the IManagedPolicy protocol because it has no method named '__jsii_proxy_class__'
  NoneType: is not an instance of NoneType

Link to the service’s CDK Construct Library API reference page.

https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_iam-readme.html

Maturity: CloudFormation Resources Only

Stable

Implementation

The issue was traced back to the version bump of typeguard from 2.13.3 to 4.3.0. We had to manually lock the typeguard version back to 2.13.3 to resolve the issue and successfully complete the deployment.

Action Needed: Update the requirements to lock typeguard to 2.13.3 or ensure compatibility with the latest version of typeguard to prevent future issues.