Ask which release line a bug report is on
Merged
MA
4mo ago+15+15+01234567890123456789-2-2-0123456789
With both the 2.x stable line and the 1.x maintenance line supported, the bug form's "I confirm that I'm using the latest version" checkbox is ambiguous for a 1.x reporter.
Motivation and Context
Rewords the check as "the newest release of my line" and adds a required Release line dropdown (2.x / 1.x) so triage can see the major at a glance.
How Has This Been Tested?
The form YAML parses and follows the same dropdown schema as v2-feedback.yaml; GitHub only renders issue forms from the default branch, so the live check is after merge.
Breaking Changes
None.
Types of changes
- Bug fix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to change)
- Documentation update
Checklist
- I have read the MCP Documentation
- My code follows the repository's style guidelines
- New and existing tests pass locally
- I have added appropriate error handling
- I have added or updated documentation as needed