chore(deps-dev): Bump typescript from 6.0.3 to 7.0.2#42
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps [typescript](https://github.com/microsoft/TypeScript) from 6.0.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
Bot
added
dependencies
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe ChangesDependency Update
Estimated code review effort: 1 (Trivial) | ~2 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
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
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis 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
##[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
##[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
| "tailwindcss": "^4.3.2", | ||
| "tw-animate-css": "1.4.0", | ||
| "typescript": "^6.0.3", | ||
| "typescript": "^7.0.2", |
There was a problem hiding this comment.
🗄️ 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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps typescript from 6.0.3 to 7.0.2.
Commits
Maintainer changes
This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.
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 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)