chore(deps): update dependency typescript to v7 #18
Labels
No labels
automerge
bug
dependencies
duplicate
help wanted
invalid
lang
rust
migrations
opencode
question
security
type
documentation
type
enhancement
type
maintenance
type
refactor
vulnerability
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Personal/backstage!18
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/typescript-7.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
~5.9.3→~7.0.0Release Notes
microsoft/TypeScript (typescript)
v7.0.2: TypeScript 7.0.2Compare Source
https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/
This tag was originally released at: https://github.com/microsoft/typescript-go/releases/tag/typescript%2Fv7.0.2
v6.0.3: TypeScript 6.0.3Compare Source
For release notes, check out the release announcement blog post.
Downloads are available on:
v6.0.2: TypeScript 6.0Compare Source
For release notes, check out the release announcement blog post.
Downloads are available on:
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.
7fb656f9281bcad832901bcad83290f69c983206⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below:
File name: bun.lock
Review Summary
This PR bumps the root devDependency
typescriptfrom~5.9.3to~7.0.0. The change itself is a one-line manifest edit, but as it stands it is not mergeable:bun.lockwas not updated (its Bun version could not parselockfileVersion: 2), sopackage.jsonnow requests TS 7 while the lockfile still resolves 5.9.3. In this repo the lockfile must be preserved (AGENTS.mdexplicitly says keepbun.lock), and anybun install --frozen-lockfile/bun run tsccheck will either error or silently use the old version. The lockfile needs regenerating with the workspace's own Bun 1.4.4 before this is reviewed for real.typescript-go), a different implementation with behavior differences intscoutput,skipLibCheck/checking edge cases, and plugin/tooling support. Backstage 1.56's@backstage/cliis only validated against the TS 5.x line; generated types,d.tsemit, and the Backstage CLI's webpack/ts-loader path may not tolerate TS 7 yet. Worth confirmingbun run tsc,bun run build:app, andbun run build:backendactually pass on this branch before merging rather than relying on Renovate's confidence badge.~7.0.0only allows patch releases within 7.0.x, which is consistent with the existing convention. No security, performance, or runtime impact — TypeScript is a dev-time-only tool here.Overall: sensible to keep the PR open and let Renovate retry with a fixed Bun, but it should not merge as-is.
*🤖 Review by opencode (opencode/mimo-v2.6-flash-free) — verdict: changes
Code review findings from opencode.
@ -51,3 +51,3 @@"node-gyp": "^13.1.0","prettier": "^3.10.1","typescript": "~5.9.3""typescript": "~7.0.0"View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.