Repository navigation
deps: bump typescript from 5.9.3 to 7.0.2 in /plugins/diff-explorer in the npm group across 1 directory - #44
Closed
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the npm group with 1 update in the /plugins/diff-explorer directory: [typescript](https://github.com/microsoft/TypeScript). Updates `typescript` from 5.9.3 to 7.0.2 - [Release notes](https://github.com/microsoft/TypeScript/releases) - [Commits](microsoft/TypeScript@v5.9.3...v7.0.2) --- updated-dependencies: - dependency-name: typescript dependency-version: 7.0.2 dependency-type: direct:development update-type: version-update:semver-major dependency-group: npm ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Collaborator
|
@dependabot ignore this major version — from bb thread thr_ahpedf2ujf |
Collaborator
|
Closing: diff-explorer is not deployed, and TypeScript 7 is an unverified major release. Take it deliberately when diff-explorer is next worked on. — from bb thread thr_ahpedf2ujf |
Contributor
Author
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/plugins/diff-explorer/npm-b7ceb5d816
branch
October 20, 2026 13:51
trotterdylan
added a commit
that referenced
this pull request
Nov 9, 2026
…284) Implements [BB-250](https://linear.app/bit-complete/issue/BB-250/stewards-filing-a-child-issue-on-github-attaches-it-as-a-native-sub). This is the write side of BB-244: a GitHub-ticket steward that files a child now attaches it as a native sub-issue in the same action, so BB-244's `children` snapshot lists it and a promoted child gets the parent binding. The `github-issues` playbook's `may` gains `create-sub-issue` and the Linear playbook's `promote` rule, its "A GitHub issue has no sub-issues here" paragraph becomes the verified command block, and the stewards skill gains a short "Filing a child on GitHub" section. The Linear playbook and Linear skill text are unchanged. > **Restart note.** Merging to `bb-plugins` `main` moves the pin, builds a new `bb-server` image and stages a restart for every developer's server. Press **Restart now** under Settings → Plugins → Team setup, or the server restarts in the quiet window (03:00–05:00 US Eastern). ## Classification owner-reviewed: `plugins/stewards/templates.ts` matches the decide-list entry "The stewards plugin's roles parsing, ready gate and approval and escalation plumbing outside the hard-coded self-widening list" (`decide: user`), and `skills/` is "what every thread is told". Per `.bb/AGENTS.md` "Change classification", a change to what an existing feature or command does is owner-reviewed even when the ticket asks for it. ## What changes - **`plugins/stewards/templates.ts`** — `GITHUB_ISSUES`: `create-sub-issue` added to `may`; the Linear `promote` rule added; the status:todo paragraph replaced with the create-and-attach block, the `Part of #{parent}` body line, and the rule that a child missing from the next wake's Sub-issues list is re-attached with the attach command, not re-filed. - **`plugins/stewards/skills/stewards/SKILL.md`** — a new `### Filing a child on GitHub` with the same commands. - **`plugins/stewards/config.test.ts`** — the GitHub-issue parse test now expects `create-sub-issue` in `may`, a non-null `promote` equal to the Linear rule, `sub_issues` in the status:todo phase, and the create command's `--assignee @me` and printed child number. - **`plugins/stewards/skill.test.ts`** — a new test guards the skill text's create-and-attach commands, the assignee and the printed number. The block, in both copies: ``` n=$(gh issue create --repo {owner}/{repo} --title "…" --body "Part of #{parent} …" --assignee @me | grep -oE '[0-9]+$') echo "filed child #$n" gh api -X POST repos/{owner}/{repo}/issues/{parent}/sub_issues -F sub_issue_id=$(gh api repos/{owner}/{repo}/issues/$n --jq .id) ``` Three corrections the hand run forced, all now in the shipped commands: 1. The spec sketched `gh issue create … --json number,id --jq '.id'` (or `gh issue view <n> --json id --jq .id`). Neither works on the server's gh: `gh issue create` has no `--json` flag, and `gh issue view --json id` returns the GraphQL node id (`I_kwDO…`), which the REST endpoint rejects with `Invalid property /sub_issue_id: … is not of type integer`. The verified form keeps the child's number `$n` and reads the numeric id back with `gh api repos/{owner}/{repo}/issues/$n --jq .id`; `-F` (not `-f`) sends `sub_issue_id` as an integer. 2. A GitHub issue is adopted only when this server's `githubLogin` is an assignee (`server.ts`, `adoptionKind`), so the create carries `--assignee @me`. Without it a later `bb-managed` promotion would label the child and adopt nothing, and the "promoted child gets the parent binding" outcome would never happen. 3. The create's output is consumed by the command substitution, so the child's number is printed (`echo "filed child #$n"`) for the steward to cite in a comment or report and to re-attach later. ## Testing - `cd bb-plugins/plugins/stewards && npm run typecheck`: pass. - `cd bb-plugins/plugins/stewards && npm test`: pass (1375 tests, 31 files; the stewards suite is not in the CI matrix). - Hand verification on `bitcomplete/sred` with the server's `gh` login (`trotterdylan`, ADMIN), creating a throwaway parent and child, attaching, listing, then closing both: ``` $ parent=$(gh issue create --repo bitcomplete/sred --title "BB-250 verify3 parent" --body "…" | grep -oE '[0-9]+$') parent = #44 $ n=$(gh issue create --repo bitcomplete/sred --title "BB-250 verify3 child" --body "Part of #44 …" --assignee @me | grep -oE '[0-9]+$') filed child #45 $ gh api -X POST repos/bitcomplete/sred/issues/44/sub_issues -F sub_issue_id=$(gh api repos/bitcomplete/sred/issues/45 --jq .id) --jq '.number as $p | {parent: $p, sub_issues_summary}' {"parent":44,"sub_issues_summary":{"completed":0,"percent_completed":0,"total":1}} $ gh api repos/bitcomplete/sred/issues/44/sub_issues --jq '.[] | {number, title, id, assignees: [.assignees[].login]}' {"assignees":["trotterdylan"],"id":6277677758,"number":45,"title":"BB-250 verify3 child"} ``` Both throwaway issues were closed. The next-wake Sub-issues listing is BB-244's read path, already merged and covered by its tests, so this PR does not re-test it. _— from bb thread thr_szeffytv72_
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 the npm group with 1 update in the /plugins/diff-explorer directory: typescript.
Updates
typescriptfrom 5.9.3 to 7.0.2Release notes
Sourced from typescript's releases.
Commits
1e4744dMerge branch 'main' into ts7-releasea5a219cmicrosoft/typescript-go#4558ecfe30dUpdate status localization5de25b5Hide executable name in TypeScript statusd7ce74aShow bundled TypeScript version for packaged servers29be66aCorrect TS 7 release version to 7.0.2ed2bd1bMerge branch 'main' into ts7-release8873075Bump the github-actions group across 1 directory with 3 updates (microsoft/ty...9427131Set up stable / nightly extension split, other prep (microsoft/typescript-go#...d4eaca5microsoft/typescript-go#4549Maintainer 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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions