Bump aws-cdk-lib from 2.142.1 to 2.260.0 in /apps/web - #199
Bump aws-cdk-lib from 2.142.1 to 2.260.0 in /apps/web#199dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [aws-cdk-lib](https://github.com/aws/aws-cdk/tree/HEAD/packages/aws-cdk-lib) from 2.142.1 to 2.260.0. - [Release notes](https://github.com/aws/aws-cdk/releases) - [Changelog](https://github.com/aws/aws-cdk/blob/main/CHANGELOG.v2.alpha.md) - [Commits](https://github.com/aws/aws-cdk/commits/v2.260.0/packages/aws-cdk-lib) --- updated-dependencies: - dependency-name: aws-cdk-lib dependency-version: 2.260.0 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4d39d29117
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "peerDependencies": { | ||
| "constructs": "^10.0.0" | ||
| "constructs": "^10.5.0" | ||
| } |
There was a problem hiding this comment.
Align constructs with the new CDK peer range
In apps/web, package.json still pins constructs to 10.3.0, but this new aws-cdk-lib@2.260.0 lock entry requires constructs@^10.5.0; npm ls aws-cdk-lib constructs --package-lock-only now reports the tree as invalid. The PR and CD workflows both run npm ci in apps/web, so dependency installation/validation will be blocked until constructs is bumped or the CDK version is kept within the compatible peer range.
Useful? React with 👍 / 👎.
Bumps aws-cdk-lib from 2.142.1 to 2.260.0.
Release notes
Sourced from aws-cdk-lib's releases.
... (truncated)
Changelog
Sourced from aws-cdk-lib's changelog.
... (truncated)
Commits
f266a47feat: update L1 CloudFormation resource definitions (#38151)318f645fix(core): stack traces contain decorator paths (#38130)2f9ae95fix(bundling): docker build can be skipped if already performed (#38134)aeafa63docs(pipelines): clarify format of DockerHub creds (#38132)baa9e1dfix(lambda-nodejs): reuse posixShellEscape for Docker bundling file operation...e360dd9feat(core): add external traces to ConstructError (#38131)5619d43Merge branch 'main' into merge-back/2.259.06bb9d75fix(core): weak cross-stack references fail for list attributes (#37948)c77a08cfeat(core): append external stack traces to metadata if available (#38124)772eebachore: update analytics metadata blueprintsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.