The bug report template's version placeholder still shows 0.2.2
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- swift
- Domain
- documentation
Research direction
Read CONTRIBUTING.md, then inspect .github/ISSUE_TEMPLATE/bug_report.yml lines 34-48 and compare the About location with the app or Sources/UttrflowUX. Update the version and macOS placeholders while keeping the description accurate, then run make verify with the specified DEVELOPER_DIR; done means the template reflects current formats and verification passes.
Written by the indexing model from the issue text.
Description
What happens
.github/ISSUE_TEMPLATE/bug_report.yml:38 uses placeholder: "0.2.2" for the Uttrflow version, and line 46 uses "26.1" for macOS. Releases moved to calendar versions with 2026.9.14 (see RELEASING.md:20), and the app requires macOS 26 or later.
Why it matters
The placeholder is an example of what to type. An old semantic version suggests the reporter is looking in the wrong place, or that the project still ships that version.
How to check
Open the "Bug report" form on the Issues page, or read lines 34-48 of the template.
Acceptance criteria
- The version placeholder shows a calendar version in the current format, for example
2026.9.14. - The macOS placeholder shows a current macOS 26 version.
- The description ("The foot of the sidebar, or Uttrflow → About.") is still accurate; check it against the app or
Sources/UttrflowUXand fix it if not.
Where to start
.github/ISSUE_TEMPLATE/bug_report.yml- Tests to extend: none;
make verifystill has to pass. - Before pushing, run
make verify(export DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer first). It is the same command CI runs, and it enforces the 95% coverage floor per module. - Read CONTRIBUTING.md first, and say on this issue that you are taking it.
Size: XS, under an hour.
- Dominant language
- Swift
- Stars
- 4
- Forks
- 17
- Avg merge
- 18h 15m
- Merged PRs (30d)
- 442
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from uttrflow/uttrflow-swift
-
Docs/performance.md says the clipboard panel waits for catchUp; toggleQuickPanel no longer waits Openarea:docs documentation good first issue P2
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
uttrflow/uttrflow-swift#1032 ·
-
area:docs documentation good first issue P2
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
uttrflow/uttrflow-swift#1023 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
uttrflow/uttrflow-swift#827 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
uttrflow/uttrflow-swift#802 ·
-
area:general enhancement good first issue P2
Difficulty 2/5 Under an hour Newbie friendliness 92/100
uttrflow/uttrflow-swift#755 ·
All issues in uttrflow/uttrflow-swift
Similar issues
-
type: docs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
googleapis/google-cloud-swift#971 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bitcoindevkit/bdk-ffi#1125 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mozilla-mobile/firefox-ios#35743 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
manaflow-ai/cmux#13417 ·
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ionic-team/capacitor#8616 ·