Release v1.4.0
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 15/100
调研方向
Start by checking the milestone’s open issues and its “Done when” criteria; this release depends on both being complete. Follow the Directory.Build.props version bump through the three “Build and test” jobs, then inspect the merged main commit before tagging v1.4.0. Verify the draft AppImage in WSLg and the listed update checks across Windows, Ubuntu and macOS; done means the release is published and ROADMAP.md records it under Shipped.
由索引模型根据 Issue 内容生成。
描述
Release 1.4.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.4.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.4.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.3.0 on Windows finds 1.4.0 in Settings › Updates, updates, restarts into it and keeps its library, and its bundled
prompuffmoves to 1.4.0 too update-check.yml, run by hand, finds 1.4.0 from 1.3.0 on Windows, Ubuntu and macOS
- a portable 1.3.0 on Windows finds 1.4.0 in Settings › Updates, updates, restarts into it and keeps its library, and its bundled
- A
docs: record the 1.4.0 releasepull request adds the row to Shipped in ROADMAP.md and a "Checked for 1.4.0" decision with what was checked by hand.
Done when
-
v1.4.0is published on the releases page, and the checks above passed. - ROADMAP.md lists it under Shipped.
- 主要语言
- C#
- 星标
- 0
- 派生
- 1
- 平均合并
- 1 小时 51 分钟
- 30 天内合并 PR
- 13
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
hazeliscoding/prompuff 的其他 Issue
-
enhancement
难度 2/5 1-3 小时 新手友好度 78/100
hazeliscoding/prompuff#34 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
hazeliscoding/prompuff#22 ·
维护者通常 1 天内回复
-
good first issue
难度 2/5 1-3 小时 新手友好度 90/100
hazeliscoding/prompuff#14 ·
维护者通常 1 天内回复
-
good first issue
难度 1/5 1-3 小时 新手友好度 92/100
hazeliscoding/prompuff#13 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 88/100
hazeliscoding/prompuff#12 ·
维护者通常 1 天内回复
查看 hazeliscoding/prompuff 的全部 Issue
相似的 Issue
-
[BUG]: Position intent set on a simple order is dropped when it becomes a bracket, OCO or OTO order可能已有人在做 @RaphaelFakhri 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
alpacahq/alpaca-trade-api-csharp#903 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 64/100
joinrpg/joinrpg-net#5752 ·
维护者通常 1 天内回复
-
bug ux
难度 2/5 1-3 小时 新手友好度 78/100
CodeForFire/lagebuch#714 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
dimitar-radenkov/Pointframe#294 ·
维护者通常 1 天内回复
-
kind/feature-request
难度 2/5 1-3 小时 新手友好度 68/100
Altinn/altinn-correspondence#2154 ·
维护者通常 1 天内回复