Repository navigation
chore(deps): bump typescript from 6.0.3 to 7.0.2 - #60
Merged
Merged
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:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
SilverKnightKMA
enabled auto-merge (squash)
July 20, 2026 04:18
This was referenced Jul 20, 2026
SilverKnightKMA
added a commit
that referenced
this pull request
Jul 20, 2026
) PR #64 misdiagnosed the lingering branch as a side effect of reusing a fixed branch name. The real cause is a long-standing GitHub platform bug (orgs/community#63409): when a PR is merged via a bot/App token (actor: github-actions[bot]), the repo setting delete_branch_on_merge is silently ignored. User-merged PRs on the same repo delete fine. Evidence from this repo's timeline: - PRs #44, #45, #47, #55, #62 (merged_by=github-actions[bot]): no auto-delete; branches lingered until manually removed. - PRs #58, #59, #60 (merged_by=SilverKnightKMA): auto-deleted within 1 second of merge. Renaming the branch per run (PR #64) only stops branch reuse; it does not delete the merged branch. Without this workflow, merged branches would accumulate indefinitely one per week. This workflow explicitly deletes the head branch on PR close (merged), scoped to same-repo automation branches (automated/*, dependabot/*, deps/*, chore/*) or trusted bot authors. Fork branches are skipped and deletion is idempotent.
This was referenced Sep 14, 2026
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
1 participant
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)