feat: validate CDK apps before deployment - #23
Merged
Conversation
dannysteenman
approved these changes
Aug 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CDK validation now runs before each environment deploy, so CloudFormation config errors stop before the deployment starts. The local task doesn't need AWS credentials, CI doesn't turn off online checks, and the pinned CLI won't drift from Projen.
This also moves
aws-cdk-libto 2.263.0 and keeps the workflow CLI version in Projen's source of truth.Checks
uv run projen validateuv run projen dev:validate --no-onlineuv run npx --yes aws-cdk@2.1130.0 --unstable=validate validate --no-onlinePYTHONPATH=src uv run projen builduv run ruff check .uv run ty check