chore(deps): bump the aws-cdk group across 1 directory with 2 updates
Bumps the aws-cdk group with 2 updates in the / directory: @aws-cdk/toolkit-lib and aws-cdk.
Updates @aws-cdk/toolkit-lib from 1.1.1 to 1.2.0
Release notes
Sourced from @aws-cdk/toolkit-lib's releases.
@aws-cdk/toolkit-lib@v1.2.01.2.0 (2025-06-19)
Features
@aws-cdk/toolkit-lib@v1.1.21.1.2 (2025-06-18)
Commits
0cba976feat(toolkit-lib):fromAssemblyDirectorycan ignore missing context (#611)e9c24a6chore: use isolatedModules tsconfig everywhere (#620)85979f2chore(toolkit-lib): set test timeout to 10s (#618)fafb1f6chore(deps): upgrade dependencies (#615)e243b11chore(toolkit-lib): include declaration maps so that API extractor can locate...- See full diff in compare view
Updates aws-cdk from 2.1018.1 to 2.1019.1
Release notes
Sourced from aws-cdk's releases.
[email protected]
2.1019.1 (2025-06-19)
Bug Fixes
[email protected]
2.1019.0 (2025-06-18)
Features
Bug Fixes
Commits
76ac13cfix: revert "retain type of context values and not convert them to string" (#...e9c24a6chore: use isolatedModules tsconfig everywhere (#620)fafb1f6chore(deps): upgrade dependencies (#615)6250b39fix(cli): retain type of context values and not convert them to string (#595)bdf1f66feat(cli): aws-cdk bundle is now targeting node18 (#610)c64f63achore(node-bundle): produce a bundle metafile by default (#607)- See full diff in compare view
Dependabot 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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions
Quality Gate passed
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
Looks like these dependencies are updatable in another way, so this is no longer needed.