From c8241dad06267d495646ce31cd4040618044fd91 Mon Sep 17 00:00:00 2001 From: cliffhall Date: Fri, 31 Jul 2026 19:18:27 -0400 Subject: [PATCH 1/4] chore: restore repo files dropped by the v2 tree swap MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A sweep of the pre-swap tree (ac3c1a12) against v2/main turned up 14 files the tree swap dropped and that were never restored to either branch. Most are correctly gone (v1 CI workflows, v1 sample-config, husky hook, two 0-byte files, v1-specific prettier config). These four are worth having: - .github/dependabot.yml — rewritten, not restored. v1's covered only github-actions at /; this covers github-actions plus the six npm manifests v2 actually has (root + four clients), monthly rather than weekly, grouped to one PR per ecosystem/directory, targeting v2/main, and labeled `v2` so the version-label rule holds for bot PRs too. - .github/ISSUE_TEMPLATE/bug_report.md — rewritten. v1's asked for an "Inspector Version e.g. 0.16.5" and had no client or version field. Under the issues-only policy this template is the primary intake, so it now asks the routing questions first (v1 vs v2, which client) and points at the prompt-not-a-diff path. - .gitattributes — restored byte-for-byte (package-lock.json linguist-generated=true). More useful in v2 than v1: there are now six lockfiles, and they dominate dependency-bump diffs. - CODE_OF_CONDUCT.md — restored byte-for-byte, so GitHub surfaces it as a community standard. Left unformatted deliberately: it is verbatim upstream Contributor Covenant text, v1 listed it in .prettierignore for that reason, and no v2 format glob reaches root markdown. CONTRIBUTING.md is deliberately not restored here — it is handled by renaming CONTRIBUTORS.md to that name, which also lights up GitHub's contributing banner without leaving two files to keep in sync. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01YAt8rqxysNbhYWLhoRm3fU --- .gitattributes | 1 + .github/ISSUE_TEMPLATE/bug_report.md | 72 +++++++++++++++ .github/dependabot.yml | 88 ++++++++++++++++++ CODE_OF_CONDUCT.md | 128 +++++++++++++++++++++++++++ 4 files changed, 289 insertions(+) create mode 100644 .gitattributes create mode 100644 .github/ISSUE_TEMPLATE/bug_report.md create mode 100644 .github/dependabot.yml create mode 100644 CODE_OF_CONDUCT.md diff --git a/.gitattributes b/.gitattributes new file mode 100644 index 000000000..cf9687215 --- /dev/null +++ b/.gitattributes @@ -0,0 +1 @@ +package-lock.json linguist-generated=true diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100644 index 000000000..8e2db121d --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -0,0 +1,72 @@ +--- +name: Bug report +about: Report something broken in the Inspector +title: "" +labels: "" +assignees: "" +--- + + + +**Which version?** + +- [ ] v2 — current, published as `@modelcontextprotocol/inspector@latest` +- [ ] v1 — deprecated, `@v1-latest` (security and bug fixes only) + +**Inspector version** + + + +**Which client?** + +- [ ] Web +- [ ] CLI +- [ ] TUI +- [ ] All / shared core + +**What happened** + + + +**What you expected instead** + +**Steps to reproduce** + +1. +2. +3. + + + +**Environment** + +- OS: +- Node version: +- Browser (web client only): +- MCP server under inspection: + +**Logs, errors, or screenshots** + + + +**Already prototyped a fix?** + + diff --git a/.github/dependabot.yml b/.github/dependabot.yml new file mode 100644 index 000000000..a4c691790 --- /dev/null +++ b/.github/dependabot.yml @@ -0,0 +1,88 @@ +version: 2 + +# Version updates target `v2/main` (the develop branch), not the default +# branch — `main` is release-only and takes milestone merges from `v2/main`. +# +# Two things to know about this file: +# 1. Dependabot reads it from the DEFAULT branch (`main`). Changes here are +# inert until the next milestone merge carries them there. +# 2. `target-branch` scopes VERSION updates. Dependabot SECURITY updates are +# enabled in repo settings, not here, and always target the default +# branch — they kept working while this file was missing entirely +# (see #1833, #1840). +# +# v2 is not an npm workspace: the root and each client under `clients/*` carry +# their own package.json + lockfile, so each needs its own entry. + +updates: + - package-ecosystem: "github-actions" + directory: "/" + target-branch: "v2/main" + schedule: + interval: "monthly" + labels: + - "v2" + groups: + github-actions: + patterns: + - "*" + + - package-ecosystem: "npm" + directory: "/" + target-branch: "v2/main" + schedule: + interval: "monthly" + labels: + - "v2" + groups: + root-dependencies: + patterns: + - "*" + + - package-ecosystem: "npm" + directory: "/clients/web" + target-branch: "v2/main" + schedule: + interval: "monthly" + labels: + - "v2" + groups: + web-dependencies: + patterns: + - "*" + + - package-ecosystem: "npm" + directory: "/clients/cli" + target-branch: "v2/main" + schedule: + interval: "monthly" + labels: + - "v2" + groups: + cli-dependencies: + patterns: + - "*" + + - package-ecosystem: "npm" + directory: "/clients/tui" + target-branch: "v2/main" + schedule: + interval: "monthly" + labels: + - "v2" + groups: + tui-dependencies: + patterns: + - "*" + + - package-ecosystem: "npm" + directory: "/clients/launcher" + target-branch: "v2/main" + schedule: + interval: "monthly" + labels: + - "v2" + groups: + launcher-dependencies: + patterns: + - "*" diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 000000000..05c32c605 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,128 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +We as members, contributors, and leaders pledge to make participation in our +community a harassment-free experience for everyone, regardless of age, body +size, visible or invisible disability, ethnicity, sex characteristics, gender +identity and expression, level of experience, education, socio-economic status, +nationality, personal appearance, race, religion, or sexual identity +and orientation. + +We pledge to act and interact in ways that contribute to an open, welcoming, +diverse, inclusive, and healthy community. + +## Our Standards + +Examples of behavior that contributes to a positive environment for our +community include: + +* Demonstrating empathy and kindness toward other people +* Being respectful of differing opinions, viewpoints, and experiences +* Giving and gracefully accepting constructive feedback +* Accepting responsibility and apologizing to those affected by our mistakes, + and learning from the experience +* Focusing on what is best not just for us as individuals, but for the + overall community + +Examples of unacceptable behavior include: + +* The use of sexualized language or imagery, and sexual attention or + advances of any kind +* Trolling, insulting or derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or email + address, without their explicit permission +* Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Enforcement Responsibilities + +Community leaders are responsible for clarifying and enforcing our standards of +acceptable behavior and will take appropriate and fair corrective action in +response to any behavior that they deem inappropriate, threatening, offensive, +or harmful. + +Community leaders have the right and responsibility to remove, edit, or reject +comments, commits, code, wiki edits, issues, and other contributions that are +not aligned to this Code of Conduct, and will communicate reasons for moderation +decisions when appropriate. + +## Scope + +This Code of Conduct applies within all community spaces, and also applies when +an individual is officially representing the community in public spaces. +Examples of representing our community include using an official e-mail address, +posting via an official social media account, or acting as an appointed +representative at an online or offline event. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported to the community leaders responsible for enforcement at +mcp-coc@anthropic.com. +All complaints will be reviewed and investigated promptly and fairly. + +All community leaders are obligated to respect the privacy and security of the +reporter of any incident. + +## Enforcement Guidelines + +Community leaders will follow these Community Impact Guidelines in determining +the consequences for any action they deem in violation of this Code of Conduct: + +### 1. Correction + +**Community Impact**: Use of inappropriate language or other behavior deemed +unprofessional or unwelcome in the community. + +**Consequence**: A private, written warning from community leaders, providing +clarity around the nature of the violation and an explanation of why the +behavior was inappropriate. A public apology may be requested. + +### 2. Warning + +**Community Impact**: A violation through a single incident or series +of actions. + +**Consequence**: A warning with consequences for continued behavior. No +interaction with the people involved, including unsolicited interaction with +those enforcing the Code of Conduct, for a specified period of time. This +includes avoiding interactions in community spaces as well as external channels +like social media. Violating these terms may lead to a temporary or +permanent ban. + +### 3. Temporary Ban + +**Community Impact**: A serious violation of community standards, including +sustained inappropriate behavior. + +**Consequence**: A temporary ban from any sort of interaction or public +communication with the community for a specified period of time. No public or +private interaction with the people involved, including unsolicited interaction +with those enforcing the Code of Conduct, is allowed during this period. +Violating these terms may lead to a permanent ban. + +### 4. Permanent Ban + +**Community Impact**: Demonstrating a pattern of violation of community +standards, including sustained inappropriate behavior, harassment of an +individual, or aggression toward or disparagement of classes of individuals. + +**Consequence**: A permanent ban from any sort of public interaction within +the community. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], +version 2.0, available at +https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. + +Community Impact Guidelines were inspired by [Mozilla's code of conduct +enforcement ladder](https://github.com/mozilla/diversity). + +[homepage]: https://www.contributor-covenant.org + +For answers to common questions about this code of conduct, see the FAQ at +https://www.contributor-covenant.org/faq. Translations are available at +https://www.contributor-covenant.org/translations. From 5d6f3d96c29da690ebf69713226719d7d0d88736 Mon Sep 17 00:00:00 2001 From: cliffhall Date: Fri, 31 Jul 2026 20:34:52 -0400 Subject: [PATCH 2/4] docs(dependabot): state the documented target-branch/security-update rule MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Copilot review: the comment read as if `target-branch` had no bearing on security updates. Per GitHub's Dependabot options reference, an entry whose `target-branch` names a non-default branch is not applied to security updates at all — so the schedule/labels/groups here shape version updates only, and security PRs continue to be raised against the default branch. Comment-only; the configured settings are unchanged. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01YAt8rqxysNbhYWLhoRm3fU --- .github/dependabot.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index a4c691790..e443c9bc7 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -7,9 +7,12 @@ version: 2 # 1. Dependabot reads it from the DEFAULT branch (`main`). Changes here are # inert until the next milestone merge carries them there. # 2. `target-branch` scopes VERSION updates. Dependabot SECURITY updates are -# enabled in repo settings, not here, and always target the default +# enabled in repo settings, not here, and are raised against the default # branch — they kept working while this file was missing entirely -# (see #1833, #1840). +# (see #1833, #1840). Per GitHub's Dependabot options reference, an entry +# whose `target-branch` names a non-default branch is NOT applied to +# security updates, so the schedule/labels/groups below shape version +# updates only. Re-confirm security PRs still appear after this lands. # # v2 is not an npm workspace: the root and each client under `clients/*` carry # their own package.json + lockfile, so each needs its own entry. From c7fbf350f726663f95d8d6ffb86d7ae625d4a223 Mon Sep 17 00:00:00 2001 From: cliffhall Date: Fri, 31 Jul 2026 20:38:33 -0400 Subject: [PATCH 3/4] docs: correct the branch description and the labeling ask MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Two suppressed Copilot comments, both correct: - dependabot.yml called `main` "release-only". It isn't — README.md and AGENTS.md both describe it as the legacy v1 implementation taking security and bug fixes only. Reworded to match, keeping the point that matters (Dependabot reads config from the default branch). - bug_report.md asked reporters to label the issue `v2`/`v1`, which most external reporters have no permission to do. It now asks only for the version checkbox and says a maintainer labels it at triage. Comment/prose only; no configured Dependabot setting changed. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01YAt8rqxysNbhYWLhoRm3fU --- .github/ISSUE_TEMPLATE/bug_report.md | 5 +++-- .github/dependabot.yml | 5 +++-- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index 8e2db121d..a038f0661 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -10,8 +10,9 @@ assignees: "" Issues are how work reaches the Inspector — we accept issues, not pull requests. See CONTRIBUTORS.md for the full policy. -Please label this issue `v2` (or `v1`, if it is a security or bug fix for the -deprecated v1 line). When in doubt, it's `v2`. +Just tick the version below — a maintainer applies the `v1` / `v2` label +during triage (most reporters can't set labels themselves). When in doubt, +it's v2. --> **Which version?** diff --git a/.github/dependabot.yml b/.github/dependabot.yml index e443c9bc7..e375a894f 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -1,7 +1,8 @@ version: 2 -# Version updates target `v2/main` (the develop branch), not the default -# branch — `main` is release-only and takes milestone merges from `v2/main`. +# Version updates target `v2/main`, the active development branch, not the +# default branch — `main` still holds the legacy v1 implementation and takes +# only security and bug fixes (see README.md "Repo status"). # # Two things to know about this file: # 1. Dependabot reads it from the DEFAULT branch (`main`). Changes here are From 2da94c64e2196c52622a47e6c9555d02f6a50e0e Mon Sep 17 00:00:00 2001 From: cliffhall Date: Fri, 31 Jul 2026 20:45:23 -0400 Subject: [PATCH 4/4] docs(dependabot): describe main as release-only, not "legacy v1" MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Reverts the branch description introduced in c7fbf350. That change was made to match README.md:17 and AGENTS.md — but those are precisely the stale sentences PR #1866 exists to correct. `main` has not been the legacy v1 implementation since the go-live tree swap; it is the release branch holding the latest released v2, and the deprecated v1 line lives on `v1/main`. So the comment now describes the real model: v2/main is the develop branch, main is release-only and receives milestone merges, v1/main is maintenance and takes security fixes only. The rest of c7fbf350 stands — the bug_report.md change (asking reporters for the version checkbox rather than to apply a label they lack permission to set) was a genuine catch. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01YAt8rqxysNbhYWLhoRm3fU --- .github/dependabot.yml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index e375a894f..6888530a7 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -1,8 +1,9 @@ version: 2 -# Version updates target `v2/main`, the active development branch, not the -# default branch — `main` still holds the legacy v1 implementation and takes -# only security and bug fixes (see README.md "Repo status"). +# Version updates target `v2/main`, the develop branch where all v2 work lands, +# not the default branch — `main` is release-only, holding the latest released +# v2 and receiving milestone merges from `v2/main`. (The deprecated v1 line +# lives on `v1/main` and takes security fixes only.) # # Two things to know about this file: # 1. Dependabot reads it from the DEFAULT branch (`main`). Changes here are