chore(deps): bump typescript from 5.7.3 to 6.0.3 in /iac-cdk in the dev-tooling group - #28
Conversation
Bumps the dev-tooling group in /iac-cdk with 1 update: [typescript](https://github.com/microsoft/TypeScript). Updates `typescript` from 5.7.3 to 6.0.3 - [Release notes](https://github.com/microsoft/TypeScript/releases) - [Commits](microsoft/TypeScript@v5.7.3...v6.0.3) --- updated-dependencies: - dependency-name: typescript dependency-version: 6.0.3 dependency-type: direct:development update-type: version-update:semver-major dependency-group: dev-tooling ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
Superseded by #29, which adopts the same TypeScript 6.0.3 with the full test triad run against it: |
…29) Dependabot opened TypeScript 6.0.3 (#28) right after the 7.0 investigation. Tested the same way, and it came out differently: 6.0.3 tsc --noEmit exit 0 · 8/8 stack tests · cdk synth 9 stacks -> ADOPTED 7.0.2 tsc --noEmit exit 0, but ALL 8 stack tests die at startup: TypeError: Cannot read properties of undefined (reading 'fileExists') `ts-node` works with TS 6 and not with TS 7, which is the native rewrite that no longer exposes the `ts.sys` JS surface ts-node reads its tsconfig through. So the `>= 7` ignore added in #27 is drawn at the measured break point rather than at "no major upgrades", and this is the upgrade it was always going to allow through. Worth recording: the implicit-`@types` removal — the cause of the 7 x TS2591 "Cannot find name 'process'" errors seen during the 7.0 test — actually landed in **6.0**, not 7. Verified by removing `types: ["node"]` under 6.0.3 and watching them come back. So the one-line tsconfig fix shipped in #27 is precisely what unblocked this upgrade. It was correct on its own terms before either upgrade was attempted, which is the useful shape: making an implicit dependency explicit paid off one major earlier than expected. Also documented in this branch, with evidence, a HIGH Dependabot alert that CANNOT be fixed right now: brace-expansion 5.0.8 (needs 5.0.9) at node_modules/aws-cdk-lib/node_modules/brace-expansion, inBundle=true `aws-cdk-lib@2.263.0` is the latest published version and it bundles the vulnerable copy. Both remediation routes were tested and neither works: `npm audit fix` reports `fixAvailable: true`, runs, and leaves the lockfile byte-identical; an `overrides: {"brace-expansion": "^5.0.9"}` also leaves it at 5.0.8, because overrides cannot reach inside a third-party bundled tarball. This is the same shape as the earlier bundled-CVE work. It clears when upstream publishes a cdk-lib that bundles 5.0.9 — there is no action available to this repository, and claiming otherwise would be the "fixAvailable" lie repeated. Tested: 3711 passed / 6 skipped (unit + regression); IaC E2E under TS 6 — tsc exit 0, 8/8 stack tests, cdk synth 9 stacks; ruff clean; make ci green.
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
Bumps the dev-tooling group in /iac-cdk with 1 update: typescript.
Updates
typescriptfrom 5.7.3 to 6.0.3Release notes
Sourced from typescript's releases.
... (truncated)
Commits
050880cBump version to 6.0.3 and LKGeeae9dd🤖 Pick PR #63401 (Also check package name validity in...) into release-6.0 (#...ad1c695🤖 Pick PR #63368 (Harden ATA package name filtering) into release-6.0 (#63372)0725fb4🤖 Pick PR #63310 (Mark class property initializers as...) into release-6.0 (#...607a22aBump version to 6.0.2 and LKG9e72ab7🤖 Pick PR #63239 (Fix missing lib files in reused pro...) into release-6.0 (#...35ff23d🤖 Pick PR #63163 (Port anyFunctionType subtype fix an...) into release-6.0 (#...e175b69Bump version to 6.0.1-rc and LKGaf4caacUpdate LKG8efd7e8Merge remote-tracking branch 'origin/main' into release-6.0Dependabot 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 <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