Feedback form typo in Version field description (version version) #44182
Description
Feedback
The documentation feedback form has a typo in the Version field description: “Latest stable version version of Home Assistant available”.
This can confuse contributors and looks unpolished in the issue flow.
Suggested fix: replace with “Latest stable version of Home Assistant available”.
URL
I’ll parse the repository’s issue and PR contribution rules, then draft 3 ready-to-submit issue texts that match this repo’s templates and workflow. Next I’ll align each draft with a matching PR description so you can post them directly. Created 3 todos I’m now pulling the contribution sections from the repo so each draft uses the correct branch, form, and wording expected by maintainers. Searched for regex current branch|next branch|pull request|issues|feedback|contribut (**/README.md), 6 results Read Read Starting: Draft 3 compliant issue reports (2/3) I’m quickly validating the repository branches and issue configuration so the drafted issues are realistic and actionable instead of generic examples. Read Read Ran terminal command: git branch --all Completed: Draft 3 compliant issue reports (2/3) Parsed Sources - I based these drafts on feedback.yml, PULL_REQUEST_TEMPLATE.md, config.yml, and ISSUE_TEMPLATE.md. - I also verified branch state locally: only current exists in this clone, so branch guidance is a valid workflow concern. Issue Draft 1 (ready to paste) - Title: Feedback form typo in Version field description (version version) - Feedback: The documentation feedback form has a typo in the Version field description: “Latest stable version version of Home Assistant available”. This can confuse contributors and looks unpolished in the issue flow. Suggested fix: replace with “Latest stable version of Home Assistant available”. - URL: https://github.com/home-assistant/home-assistant.io/blob/current/.github/ISSUE_TEMPLATE/feedback.yml - Version: 2026.3.0 - Additional information: Location appears in the version input description in the feedback issue form. Issue Draft 2 (ready to paste) - Title: PR template branch guidance can block contributors when next branch is unavailable - Feedback: The PR template asks contributors to choose current or next, but next is not always present in active forks/clones. This can cause confusion during submission and lead to incorrect branch targeting attempts. Suggested fix: add conditional wording like “use next if it exists for that release cycle, otherwise use the active contribution branch documented by maintainers”. - URL: https://github.com/home-assistant/home-assistant.io/blob/current/.github/PULL_REQUEST_TEMPLATE.md - Version: 2026.3.0 - Additional information: This is a contributor workflow bug, not a runtime Home Assistant bug. Issue Draft 3 (ready to paste) - Title: Duplicate issue templates may drift: legacy Markdown template and issue form both define feedback flow - Feedback: The repository contains both a legacy markdown issue template and a YAML issue form for documentation feedback. Keeping both increases maintenance overhead and can create inconsistent wording over time. Suggested fix: standardize on one template path, or explicitly document why both are kept and how they should remain synchronized. - URL: https://github.com/home-assistant/home-assistant.io/blob/current/.github/ISSUE_TEMPLATE.md - Version: 2026.3.0 - Additional information: Related file: https://github.com/home-assistant/home-assistant.io/blob/current/.github/ISSUE_TEMPLATE/feedback.yml Matching PR Draft (covers all 3 issues) - Title: Improve contributor issue/PR template clarity and consistency - Proposed change: - Fix typo in feedback form (version version → version) - Clarify PR branch guidance to avoid next branch confusion - Consolidate or document coexistence of legacy and form-based issue templates - Type of change: - [x] Spelling, grammar or other readability improvements (current branch). - [x] Adjusted missing or incorrect information in the current documentation (current branch). - Additional information: - This PR fixes or closes issue: fixes #, fixes #, fixes # - Checklist: - [x] I made a change to the existing documentation and used the current branch. - [x] The documentation follows the Home Assistant documentation standards. Want me to turn these drafts into actual file edits in this repo and prepare a clean PR patch next?
Version
2026.3.0
Additional information
Location appears in the version input description in the feedback issue form.