Skip to content

Commit f37e72c

Browse files
committed
Ask which release line a bug report is on
With both the 2.x stable line and the 1.x maintenance line supported, "I confirm that I'm using the latest version" is ambiguous for a 1.x reporter. Reword the check as the newest release of the reporter's own line and add a required Release line dropdown so triage can see the major at a glance.
1 parent 6f69a37 commit f37e72c

1 file changed

Lines changed: 15 additions & 2 deletions

File tree

.github/ISSUE_TEMPLATE/bug.yaml

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,13 +11,26 @@ body:
1111
id: checks
1212
attributes:
1313
label: Initial Checks
14-
description: Just making sure you're using the latest version of MCP Python SDK.
14+
description: >
15+
Both the 2.x stable line and the 1.x maintenance line are supported, and only
16+
the newest release of each line receives fixes.
1517
options:
16-
- label: I confirm that I'm using the latest version of MCP Python SDK
18+
- label: I confirm that I'm using the newest release of my line (the latest 2.x, or the latest 1.x if I'm still on v1)
1719
required: true
1820
- label: I confirm that I searched for my issue in https://github.com/modelcontextprotocol/python-sdk/issues before opening this issue
1921
required: true
2022

23+
- type: dropdown
24+
id: release-line
25+
attributes:
26+
label: Release line
27+
description: Which major version of the SDK are you using?
28+
options:
29+
- 2.x (current stable)
30+
- 1.x (maintenance line, v1.x branch)
31+
validations:
32+
required: true
33+
2134
- type: textarea
2235
id: description
2336
attributes:

0 commit comments

Comments
 (0)