Skip to content

deps: bump typescript from 5.9.3 to 7.0.2 - #228

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/typescript-7.0.2
Closed

deps: bump typescript from 5.9.3 to 7.0.2#228
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/typescript-7.0.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 20, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps typescript from 5.9.3 to 7.0.2.

Release notes

Sourced from typescript's releases.

TypeScript 6.0.3

For release notes, check out the release announcement blog post.

Downloads are available on:

TypeScript 6.0

For release notes, check out the release announcement blog post.

Downloads are available on:

TypeScript 6.0 Beta

For release notes, check out the release announcement.

Downloads are available on:

Commits
Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Jul 20, 2026
@dependabot @github

dependabot Bot commented on behalf of github Jul 20, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: security. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot mentioned this pull request Jul 20, 2026
Closed
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/typescript-7.0.2 branch from 9a2dac4 to 39307db Compare July 21, 2026 09:10
@dependabot dependabot Bot changed the title deps: Bump typescript from 5.9.3 to 7.0.2 deps: bump typescript from 5.9.3 to 7.0.2 Aug 6, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/typescript-7.0.2 branch from 39307db to d9bbd7f Compare August 6, 2026 12:41
@catomean catomean mentioned this pull request Aug 6, 2026
Merged
@catomean

catomean commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

Re-checked 2026-08-06 — still blocked upstream, no change.

CI fails with Error: typescript-eslint does not support TS 7.0.

That is a hard version ceiling, not a stale dependency. The latest typescript-eslint (8.66.0, and @typescript-eslint/parser@8.66.0) still declares:

"typescript": ">=4.8.4 <6.1.0"

TypeScript 7.0.2 is well outside that range, so no combination of currently published packages makes this PR green.

Nothing to do until typescript-eslint ships TS 7 support. Leaving it red is correct — CI self-blocks it. Re-test by checking npm view @typescript-eslint/parser@latest peerDependencies for a typescript range that admits 7.x.

github-actions Bot pushed a commit that referenced this pull request Aug 7, 2026
@catomean @claude
fix(ci): retry runs that failed before executing any of our code (#280)
ca6f807 
* fix(ci): retry runs that failed before executing any of our code

The sweep retries CANCELLED checks but deliberately leaves genuine failures
alone. A GitHub Actions incident lands in the gap between those two: the run
fails with conclusion=failure, so it is treated as a real verdict — but it
never executed a line of this repo's code.

Consequence: during an incident EVERY open PR is stranded permanently, and
nobody is in the merge loop to notice. Today (2026-08-06, Actions major
outage, webhooks throttled to ~15%) three jobs on PR #278 died with "Failed
to resolve action download info. Error: Service Unavailable" and that PR
cannot become green again without a human running `gh run rerun --failed`.

The discriminator is precise: a job whose ONLY failed step is "Set up job"
never got as far as running our code, so it produced no verdict about it.
A real failure names a real step.

Verified against live runs:
  PR #278 outage run  -> [Set up job]                                -> infra
  PR #228 (TS 7)      -> [Verify (lint + umlauts + typecheck + build)] -> real
  PR #265 (ESLint 10) -> [Verify (lint + umlauts + typecheck + build)] -> real
  nonexistent run     -> no data -> refuses to guess

Conservative by construction: retries only when EVERY failed job in the run
failed at set-up. One real step failure anywhere and the PR is left alone.

Capped at MAX_RUN_ATTEMPTS (default 3) — an incident can last hours, and an
uncapped retry would re-run the same doomed run every sweep forever.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(ci): self-heal a base branch whose CI ended without a verdict

The sweep already knew that a cancelled/infra-failed run is noise rather than
a judgement — but only for PR checks. The base branch kept the original
"refuse and exit" behaviour, which deadlocks: the only thing that produces a
new CI run on main is a merge, and merges are exactly what the guard blocks.

Observed here on 2026-08-07. An Actions incident left main's run `failure`
with no failed job at all (Migration Drift cancelled, everything else green).
Eleven PRs sat for ~14h while every sweep exited 0 and looked healthy.

So: extract the "is this a verdict about the code?" test and apply it to the
base run too. A genuine failure still blocks — that IS a verdict. Retries are
capped by the run's own attempt counter, which is why this re-runs rather than
dispatching fresh (a new dispatch resets to attempt 1 and could churn forever).

Also drops `--failed` from the PR-side retry. A partial re-run flips SKIPPED
jobs to CANCELLED, so the PR ends up non-green for a brand new reason and needs
yet another retry — seen on #278 today.

Tested by running the real script against a fake `gh` on PATH, so this covers
shipped control flow rather than a re-description of it. Mutation-checked:
disabling the self-heal turns 3 of the 6 tests red.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/typescript-7.0.2 branch from d9bbd7f to f05d8e7 Compare August 7, 2026 19:29
@dependabot
deps: bump typescript from 5.9.3 to 7.0.2
8e06e5c 
Bumps [typescript](https://github.com/microsoft/TypeScript) from 5.9.3 to 7.0.2.
- [Release notes](https://github.com/microsoft/TypeScript/releases)
- [Commits](https://github.com/microsoft/TypeScript/commits)

---
updated-dependencies:
- dependency-name: typescript
  dependency-version: 7.0.2
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/typescript-7.0.2 branch from f05d8e7 to 8e06e5c Compare August 10, 2026 10:37
@catomean

catomean commented Aug 19, 2026

Copy link
Copy Markdown
Collaborator

Closing — confirmed upstream blocker, not fixable in this repo.

Reproduced directly on this branch: typescript-eslint refuses to load at all against TypeScript 7.0 — it's a hard guard in its own code, not a lint rule or a config issue:

```
typescript-eslint does not support TS 7.0.
Please see https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/#running-side-by-side-with-typescript-6.0 to run typescript-eslint using the TS 6 API.
See also typescript-eslint/typescript-eslint#10940 for tracking typescript-eslint's support for TS >=7.1

at Object.<anonymous> (node_modules/eslint-config-next/node_modules/typescript-eslint/dist/index.js:52:11)

```

TypeScript 7.0 is the new native (Go-based, "tsgo") compiler rewrite; typescript-eslint has an open, unresolved tracking issue (typescript-eslint/typescript-eslint#10940) and explicitly blocks import rather than degrading. The suggested escape hatch (installing TypeScript 6 side-by-side purely for typescript-eslint's API while tsc itself runs 7) is a real architectural change, not a routine dependency bump, and would need to land as its own deliberate PR once typescript-eslint ships real support.

Closing until upstream lands support. Will reopen/redo this bump once typescript-eslint#10940 resolves.

@catomean catomean closed this Aug 19, 2026
@dependabot @github

dependabot Bot commented on behalf of github Aug 19, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/typescript-7.0.2 branch August 19, 2026 00:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@catomean