chore(release): LWT 3.3.0-fork, and restore the lost 3.2.2 changelog - #269
Merged
Conversation
Two things, because the release cannot be cut correctly without the first. Restore the 3.2.2-fork changelog section. It was written by the release commit b35053c and deleted by merge 2a91170 (PR #259, apkg export): that branch predated the release, so resolving the CHANGELOG conflict took the branch side and dropped the heading, folding all fifteen items that shipped in 3.2.2 back under [Unreleased]. 3.2.2 has been tagged and on main since 2026-08-05 with no changelog of its own. The restored section is byte-identical to what b35053c published; only the heading was missing. The `### Removed` block for #266 is new work, not 3.2.2's, so it moves up into the release being cut rather than staying where the heading landed. Cut 3.3.0-fork. Minor, not patch: three Added entries — Anki deck import (#228), FSRS-6 scheduling groundwork (#238 phase 2a), and .apkg export and import. The reader fix is the one users are waiting on: selecting several words produced a term named after two SHA-256 tokens, and 3.2.x is still shipping it. Bumps ApplicationInfo::VERSION + RELEASE_DATE and package.json. `@since 3.2.2` annotations are left alone — those features did ship in 3.2.2.
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
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.
Cuts 3.3.0-fork, and first repairs a changelog bug that would otherwise be
made permanent by the release.
The 3.2.2 changelog was silently deleted
3.2.2 has been tagged and on
mainsince 2026-08-05, andApplicationInforeports it — but
grep 3.2.2 CHANGELOG.mdreturned nothing. The sections read[Unreleased] → [3.2.1-fork].The release commit
b35053cf3did write the heading. Merge2a9117053(PR #259, apkg export) removed it:
[3.2.2-fork]?aa0b366bb(first parent, PR #260)579c9c9fa(second parent, apkg branch)2a9117053(merge result)That branch was cut before the release, so resolving the CHANGELOG conflict
took the branch side. The effect isn't cosmetic: the fifteen items that
shipped in 3.2.2 — the term modal,
CurrentLanguage::resolveId(), the CRLFtag-import fix, #250, #249, the
data_hexidentity change, thirteen securityadvisories — were sitting back under
[Unreleased]. Anyone running 3.2.2 hadno changelog for their version.
It had to be fixed before the release or 3.3.0's section would have absorbed
3.2.2's content and the gap would have become permanent.
Verified by extracting both and diffing: the restored section is byte-identical
to what
b35053cf3published. The### Removedblock for #266 is new work,so it moves up into 3.3.0 rather than staying inside the restored 3.2.2.
The release
Minor rather than patch — three Added entries:
.apkgexport and import round-tripThe reader fix is the one users are actually waiting on: selecting several
words in the reader produced a term named
e6967a5826fe441a 75e3090289e2955d,and 3.2.x still ships it.
@since 3.2.2annotations in source are left alone — those features did shipin 3.2.2.
Checks
--threads=1— no errors foundApplicationInfo.php— 0 errors, 0 warningspre-existing and inside
vendor/kiwilan/php-ebook.vite.config.tsorsrc/frontend/reads thepackage version.