chore: group CDK deps in Dependabot; stop duplicating versions in tech.md#274
Merged
Conversation
Add a dedicated aws-cdk Dependabot group (aws-cdk, aws-cdk-lib, constructs) so routine version bumps land in one focused PR, and document that the CLI and library are version-coupled. Grouping only covers version updates; a security-only advisory can still bump one package alone, so the "Validate CDK synthesis" CI check remains the backstop against lib/CLI schema drift. Refresh the stale dependency list in .kiro/steering/tech.md to match the root package.json (aws-cdk-lib 2.261.0, aws-cdk 2.1129.0, constructs 10.4.3, dotenv 17.2.3, cdk-nag 2.37.55, etc.), add the previously-omitted build/test toolchain packages, and note that package.json is the source of truth. The ES2020 target and strict-null-checks claims were verified against tsconfig.json and left unchanged. Note: the aws-cdk-lib/aws-cdk versions here match the separate bump on chore/bump-aws-cdk-lib-and-cli.
tech.md restated pinned versions that also live in package.json, so it went stale on every dependency bump. Because tech.md is an always-included steering file, those stale numbers were injected into every session. Replace the version list with dependency names + roles and point to the package manifests (root package.json / package-lock.json for the CDK app, and website/package.json for the docs site) as the single source of truth, per the ci-workflows.md single-source-of-truth principle. The CDK lib/CLI coupling note is kept (it carries no specific versions).
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
|
Scan for commit: 🔒 Security Scan ResultsScanned files: 2 |
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.
What does this PR do?
🛑 Please open an issue first to discuss any significant work and flesh out details/direction — we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.
Motivation
Type of Change
Testing
npm run buildsuccessfullynpm run testand all tests passnpx cdk synthwith a sample.env(e.g. fromblueprints/dummy/samples/) and it succeedsnpm run run-pre-commitNew Blueprint Checklist (if adding a protocol)
blueprints/dummy/(reference implementation).envfiles are provided for at least one network (mainnet or testnet)blueprints/dummy/)website/docs/blueprints/(.mdx mirror importing README)Documentation
cd website && npm run buildwith no broken links (if docs changed)License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.