Repository navigation
release: 10.12.0 - the first date-based version (DeepFilterNet length fix) - #65
Merged
Merged
Conversation
Versioning moves to MM.DD.N - month, day, and the index of the release within that day, starting at 0. Today's first cut is therefore 10.12.0, and a second one today would be 10.12.1. The old 0.x numbers stay as history rather than being rewritten, and dpkg still orders them correctly (10.12.0 upgrades 0.3.1). The cost is honest: a date version no longer tells you whether a release is a patch or a breaking change, so the release notes have to carry that - which they now do, because release.yml builds the notes from the CHANGELOG section for the tag. What ships in it: - the capture fix from #61 (nextless.so behaviour, the reason for a release at all): a deep-filter utterance no longer arrives 69-97 ms shorter than it was recorded, dfDenoise() is length-preserving, and a badly short response is rejected rather than padded; - the DeepFilterNet measurement itself (bench_asr --denoise, RTF 0.13-0.16) and the README's measured cost + new Rolling back section. Bumped in the places that must agree or the pipeline notices: meson.build (which is what fcitx5-diagnose shows, via nextless-addon.conf.in), debian/changelog at 10.12.0-1 with a real weekday - validated locally with dpkg-parsechangelog before pushing, since a wrong weekday only shows up in the build - docs/nextless.1 .TH, and the CHANGELOG section rename from [Unreleased] to [10.12.0] so the release notes have something to extract. Suite 21/21. Tag follows the merge, not this commit: release.yml refuses to publish when the tag and debian/changelog disagree.
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.
Version scheme change
Per the project owner's rule, versions are now
MM.DD.N- today's firstrelease is
10.12.0, a second one on the same day would be10.12.1. Tags arev+ version. The0.xhistory is kept as-is rather than rewritten, and theordering still works: dpkg ranks
10.12.0above0.3.1, GitHub'sreleases/latestfollows the new tag, andinstall-deb.shbuilds the asset namefrom the tag so it never assumed a semver shape.
The cost, stated plainly in FINDINGS.md: a date version no longer signals
"patch vs breaking". The release notes have to carry that instead - which they
now do, since
release.ymlextracts the notes from the CHANGELOG section for thetag (
## [10.12.0]).What ships in 10.12.0
nextless.sobehaviour and.debusers otherwise never get it: adenoise: deepfilterutterance used to arrive 69-97 ms shorter than it wasrecorded;
dfDenoise()is now length-preserving.bench_asr --denoise, RTF 0.13-0.16,~1.0-1.3 s per 5-10 s utterance) with the raw JSONL committed.
section from docs(readme): write the rollback path (roadmap row 4's documentable half) #64.
Bumped in every place that has to agree
meson.buildnextless-addon.conf.in→ this is whatfcitx5-diagnoseprints (verified: the generated conf now saysVersion=10.12.0)debian/changelog10.12.0-1; weekday validated locally withdpkg-parsechangelog(timestamp parses asMon, 12 Oct 2026) - the 0.3.1 lesson was learning this only from a build failuredocs/nextless.1.THdate + versionCHANGELOG.md[Unreleased]→[10.12.0] - 2026-10-12, so the release-notes extractor finds a sectionSECURITY.md0.3.1 and everything before it, which stopped being true the moment the numbering movedrelease.ymlv0.2.0, v0.3.1as the tag shape; now states the date rule and why the mismatch gate existsSuite 21/21. The tag comes after merge, never with the bump commit - the
mismatch gate would otherwise refuse to publish (that happened once before).