Repository navigation
release: 0.3.1 - the review-debt release - #58
Merged
Merged
Conversation
Everything between v0.3.0 and here is behaviour users get by updating the package, so it needs a tag: the capture sweep no longer deleting another session's recording (#42, PR #55) and the punctuator's three-strike breaker (#47, PR #53) both live in nextless.so. The installer-side fixes (#43/#46 in #51, #41 in #52, #45/#44 in #54/#57) already reach people through raw main and the .deb metadata respectively, but they are part of the same story and belong in the changelog. Also while touching debian/changelog: there was no blank line between the 0.3.0-1 and 0.2.0-1 entries. dpkg tolerated it, Debian policy does not, and a sponsor's tooling would be the first to say so. docs/nextless.1 still advertised .TH version 0.2.0 - it drifted at the 0.3.0 bump; corrected to 0.3.1 with today's date. SECURITY.md's "reportedly affected versions" line moves with the release for the same reason.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
版本
0.3.0 → 0.3.1。合入后打v0.3.1，Release 工作流构建并发布.deb+sha256sums.txt（tag 与debian/changelog不一致它会拒发，这是那道门在起作用）。为什么要发版而不是只留在 main
v0.3.0 之后的八笔评审债里，有两笔是装在
nextless.so里的行为，用户不更新包就永远拿不到：$XDG_RUNTIME_DIR/nextless是共享固定目录，构造时的清扫会删掉另一个会话正在写的 WAV（重启竞争、双会话、边口述边跑测试）。现在按文件名里的 pid 判归属。sherpa-onnx-offline-punctuation会让之后每句话都白等 5 秒，而面板上什么都看不出来。其余几笔（#43/#46/#41/#45/#44/#48）走的是
raw/main上的安装脚本、debian/control元数据与文档，不依赖这个 tag，但同一个故事该在同一份 changelog 里。顺带修掉的两处漂移
debian/changelog里 0.3.0-1 与 0.2.0-1 两条之间没有空行。dpkg 忍了，Debian 政策不忍（policy §4.4 要求条目间恰好一个空行），sponsor 的 lintian/sbuild 会先撞上；这次加上了。docs/nextless.1的.TH还写着0.2.0/2026-10-05——0.3.0 那次 bump 漏了它。改成0.3.1/ 今天。SECURITY.md 里"reportedly affected versions"那行同样跟着走。本地
meson test20/20；dpkg-parsechangelog -S Version→0.3.1-1（2026-10-09 是 Friday，星期已核对，dpkg 会验）。合并后
git tag -a v0.3.1→ push tag → 盯 Release 工作流 → 核对资源与摘要。这条链子本身在上一次发布里已经验证过（v0.3.0 的 deb + sha256sums 都在页上）。