❗️NOTICE "Invalid Assembly Manifest" when using lib 2.203.0 with CLI 2.1017.0/2.1018.0

[rix0rrr]

Please add your +1 👍 to let us know if you are affected by this issue (please only +1 if you are encountering the actual bug described below; no need to +1 if you are seeing this notice while not affected)

Status: RESOLVED

Why am I seeing this notice?

You will receive this notice if you are on library version 2.203.0, even though you are not affected if you are not on one of the indicated CLI versions. This is an unfortunate consequence of how we can target notices: it is a giant "or" of multiple conditions, but there is no "and", so we decided to target on library version. Our apologies for any confusion.

Overview

When synthesizing using a library version of 2.203.0, and using one of the CLI versions 2.1017.0 or 2.2018.0, you will see the error:

Invalid assembly manifest:
instance.artifacts.aws-cdk-lib/feature-flag-report.type is not one of enum values: none,aws:cloudformation:stack,cdk:tree,cdk:asset-manifest,cdk:cloud-assembly
...

Instead of the usual:

This CDK CLI is not compatible with the CDK library used by your application. Please upgrade the CLI to the latest version.

Solution

Perform either of the following remediations:

• Upgrade aws-cdk-lib to 2.203.1 or higher (this will stop the notice from appearing)
• Upgrade the CLI (aws-cdk) to 2.1019.0 or higher (this will not stop the notice from appearing, but it will solve the issue)

Related Issues

• feat: report feature flag configuration into Cloud Assembly #34798
• fix: "Invalid Assembly Manifest" when used with CLI 2.1017.0 and 2.1018.0 #34880
• fix(cloud-assembly-schema): bump the version number aws-cdk-cli#677
• feat: report feature flags into Cloud Assembly #34884
• chore: notice for https://github.com/aws/aws-cdk/issues/34885 cdklabs/aws-cdk-notices#870