chore(deps-dev): Bump typescript from 6.0.3 to 7.0.2

[dependabot]

Bumps typescript from 6.0.3 to 7.0.2.

Commits

• See full diff in compare view

Maintainer changes

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

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated the TypeScript development dependency to a newer version.

Walkthrough

The typescript devDependency in package.json was updated from ^6.0.3 to ^7.0.2. No other configuration, scripts, or dependencies changed.

Changes

Dependency Update

Layer / File(s)	Summary
TypeScript version bump package.json	Updated the typescript devDependency from ^6.0.3 to ^7.0.2.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: finallyjay

Poem

A small version change takes flight,
TypeScript seven now shines bright.
One package line, no code to mend,
A tidy update from start to end. 🐇

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description states the dependency update but omits the required Summary, Test plan, Breaking changes, and Related sections.	Add the required template sections, including test results, breaking-change information, and related issue details.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly identifies the development dependency and the exact version change.

✨ Finishing Touches 💡 2

⚔️ Resolve merge conflicts 💡

• Resolve merge conflict in branch dependabot/npm_and_yarn/typescript-7.0.2

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dependabot/npm_and_yarn/typescript-7.0.2

---

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 76: The TypeScript dependency is pinned to an unpublished version, which
will break installs. Update the package.json entry for typescript to a published
npm release that exists, keeping the change limited to the dependency
declaration so consumers can install successfully.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 7ecd8e51-2938-412d-bf7d-adf359408401

📥 Commits

Reviewing files that changed from the base of the PR and between 9811798 and d088805.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• package.json

📜 Review details

⚠️ CI failures not shown inline (2)

GitHub Actions: CI / quality: chore(deps-dev): Bump typescript from 6.0.3 to 7.0.2

Conclusion: failure

View job details

##[group]Run pnpm install --frozen-lockfile
 �[36;1mpnpm install --frozen-lockfile�[0m
 shell: /usr/bin/bash -e {0}
 env:
   PNPM_HOME: /home/runner/setup-pnpm/node_modules/.bin
 ##[endgroup]
 ? Verifying lockfile against supply-chain policies (453 entries)...
 Lockfile is up to date, resolution step is skipped
 Progress: resolved 1, reused 0, downloaded 0, added 0
 Packages: +327
 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 Progress: resolved 327, reused 0, downloaded 44, added 0
 Progress: resolved 327, reused 0, downloaded 128, added 8
 Progress: resolved 327, reused 0, downloaded 294, added 20
 Progress: resolved 327, reused 0, downloaded 325, added 71
 ✗ Lockfile failed supply-chain policy check (453 entries in 5s)
 Progress: resolved 327, reused 0, downloaded 327, added 326
 Progress: resolved 327, reused 0, downloaded 327, added 327, done
 [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 21 lockfile entries failed verification:
   `@typescript/typescript-aix-ppc64`@7.0.2 was published at , within the minimumReleaseAge cutoff ()
   `@typescript/typescript-darwin-arm64`@7.0.2 was published at , within the minimumReleaseAge cutoff ()
   `@typescript/typescript-darwin-x64`@7.0.2 was published at , within the minimumReleaseAge cutoff ()
   `@typescript/typescript-freebsd-arm64`@7.0.2 was published at , within the minimumReleaseAge cutoff ()
   `@typescript/typescript-freebsd-x64`@7.0.2 was published at , within the minimumReleaseAge cutoff ()
   `@typescript/typescript-linux-arm`@7.0.2 was published at , within the minimumReleaseAge cutoff ()
   `@typescript/typescript-linux-arm64`@7.0.2 was published at , within the minimumReleaseAge cutoff ()
   `@typescript/typescript-linux-loong64`@7.0.2 was published at , within the minimumReleaseAge cutoff ()
   `@typescript/typescript-linux-mips64el`@7.0.2 was published at , within the minimumReleaseAge cutoff ()
   `@typescript/typescript-linux-ppc64`@7.0.2 was published at , within the minimumReleaseAge cutof...

---

GitHub Actions: CI / 0_quality.txt: chore(deps-dev): Bump typescript from 6.0.3 to 7.0.2

Conclusion: failure

View job details

##[group]Run pnpm install --frozen-lockfile
 �[36;1mpnpm install --frozen-lockfile�[0m
 shell: /usr/bin/bash -e {0}
 env:
   PNPM_HOME: /home/runner/setup-pnpm/node_modules/.bin
 ##[endgroup]
 ? Verifying lockfile against supply-chain policies (453 entries)...
 Lockfile is up to date, resolution step is skipped
 Progress: resolved 1, reused 0, downloaded 0, added 0
 Packages: +327
 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 Progress: resolved 327, reused 0, downloaded 44, added 0
 Progress: resolved 327, reused 0, downloaded 128, added 8
 Progress: resolved 327, reused 0, downloaded 294, added 20
 Progress: resolved 327, reused 0, downloaded 325, added 71
 ✗ Lockfile failed supply-chain policy check (453 entries in 5s)
 Progress: resolved 327, reused 0, downloaded 327, added 326
 Progress: resolved 327, reused 0, downloaded 327, added 327, done
 [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 21 lockfile entries failed verification:
   `@typescript/typescript-aix-ppc64`@7.0.2 was published at , within the minimumReleaseAge cutoff ()
   `@typescript/typescript-darwin-arm64`@7.0.2 was published at , within the minimumReleaseAge cutoff ()
   `@typescript/typescript-darwin-x64`@7.0.2 was published at , within the minimumReleaseAge cutoff ()
   `@typescript/typescript-freebsd-arm64`@7.0.2 was published at , within the minimumReleaseAge cutoff ()
   `@typescript/typescript-freebsd-x64`@7.0.2 was published at , within the minimumReleaseAge cutoff ()
   `@typescript/typescript-linux-arm`@7.0.2 was published at , within the minimumReleaseAge cutoff ()
   `@typescript/typescript-linux-arm64`@7.0.2 was published at , within the minimumReleaseAge cutoff ()
   `@typescript/typescript-linux-loong64`@7.0.2 was published at , within the minimumReleaseAge cutoff ()
   `@typescript/typescript-linux-mips64el`@7.0.2 was published at , within the minimumReleaseAge cutoff ()
   `@typescript/typescript-linux-ppc64`@7.0.2 was published at , within the minimumReleaseAge cutof...

🧰 Additional context used

📓 Path-based instructions (1)

{package.json,pnpm-lock.yaml,.npmrc}

📄 CodeRabbit inference engine (CLAUDE.md)

Use pnpm as the package manager (pnpm 10.25)

Files:

• package.json

[coderabbitai]

🗄️ Data Integrity & Integration | 🔴 Critical | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
curl -s https://registry.npmjs.org/typescript/7.0.2 | jq '.version, .dist.tarball'
curl -s https://registry.npmjs.org/typescript | jq '."dist-tags"'

Repository: finallyjay/csgo-inventory-tracker

Length of output: 1961

---

🌐 Web query:

typescript 7.0.2 npm registry published

💡 Result:

As of today, July 8, 2026, TypeScript 7.0.2 has not been published to the npm registry. The latest stable version of TypeScript remains 6.0.3, which was released on April 16, 2026 [1][2][3]. While TypeScript 7.0 is currently in its release candidate phase—with the 7.0 RC version having been announced on June 18, 2026 [4][5][6]—the 7.0.x branch has not progressed to a 7.0.2 release on npm. Users can currently access the 7.0 release candidate via the npm registry [7][5].

Citations:

• 1: https://registry.npmjs.org/typescript
• 2: https://www.npmjs.com/package/typescript
• 3: https://github.com/microsoft/TypeScript?search=1
• 4: https://devblogs.microsoft.com/typescript/announcing-typescript-7-0-rc/
• 5: https://visualstudiomagazine.com/articles/2026/06/22/typescript-7-0-rc-moves-microsofts-go-rewrite-into-the-mainline-compiler.aspx
• 6: https://www.infoworld.com/article/4191918/typescript-7-0-reaches-release-candidate-stage.html
• 7: https://www.npmjs.com/~typescript

---

typescript@7.0.2 is not published on npm. This pin will break installs; use a published release instead.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@package.json` at line 76, The TypeScript dependency is pinned to an
unpublished version, which will break installs. Update the package.json entry
for typescript to a published npm release that exists, keeping the change
limited to the dependency declaration so consumers can install successfully.

[dependabot]

Looks like typescript is up-to-date now, so this is no longer needed.