Release v1.5.0
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by checking the milestone’s other issues and its “Done when” criteria, then review the release workflow and Directory.Build.props. Follow the listed release steps: verify the build and test jobs, test the draft AppImage and update paths, then record the published release in ROADMAP.md. Done means v1.5.0 is published, the specified checks pass, and the roadmap lists it under Shipped.
Written by the indexing model from the issue text.
Description
Release 1.5.0 once every other issue in this milestone is closed and the milestone's "Done when" holds.
What to do
- A pull request titled
chore(release): 1.5.0bumps the version inDirectory.Build.props. It merges like any other change, once the three "Build and test" jobs pass. - Tag the merged commit on
mainasv1.5.0and push the tag.v*tags can't be moved or deleted, so check the commit first. The release workflow packs every platform, runs the smoke tests and opens a draft release. - Before publishing, open the draft's AppImage in WSLg with scratch folders and try the milestone's new features there.
- The owner publishes the draft. Installed copies only see published releases, and
winget.ymlsubmits it to winget. - After publishing:
- a portable 1.4.0 on Windows finds 1.5.0 in Settings › Updates, updates, restarts into it and keeps its library, and its bundled
prompuffmoves to 1.5.0 too update-check.yml, run by hand, finds 1.5.0 from 1.4.0 on Windows, Ubuntu and macOS
- a portable 1.4.0 on Windows finds 1.5.0 in Settings › Updates, updates, restarts into it and keeps its library, and its bundled
- A
docs: record the 1.5.0 releasepull request adds the row to Shipped in ROADMAP.md and a "Checked for 1.5.0" decision with what was checked by hand.
Done when
-
v1.5.0is published on the releases page, and the checks above passed. - ROADMAP.md lists it under Shipped.
- Dominant language
- C#
- Stars
- 0
- Forks
- 1
- Avg merge
- 1h 21m
- Merged PRs (30d)
- 22
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 hazeliscoding/prompuff
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hazeliscoding/prompuff#34 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hazeliscoding/prompuff#22 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
hazeliscoding/prompuff#14 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
hazeliscoding/prompuff#13 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
hazeliscoding/prompuff#12 ·
Maintainers usually reply within 1 day
All issues in hazeliscoding/prompuff
Similar issues
-
feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
stripe/stripe-dotnet#3484 ·
Maintainers usually reply within 2 days
-
bug mcp misleading small
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
accessibility help wanted macos
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
dorlugasigal/annotator#42 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
AvaloniaUI/Avalonia#22568 ·
Maintainers usually reply within 2 days
-
[bug] 截图失败日志冲爆硬盘Open
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
babalae/better-genshin-impact#3846 · 2 comments ·
Maintainers usually reply within 2 days