[unidoc-anom]

Description and links

Moves [Unreleased] in CHANGELOG.md to [0.5.0] - 2026-10-14 ahead of tagging v0.5.0, the same step 716e8dd did for 0.4.0.

[Unreleased] only covered the later changes. Eleven merged since v0.4.0 had no entry, so they are added here: the image preview (#17, #18), the in-app update notification (#19), find in the Object and XREF tabs (#15), the macOS DMG layout (#16), the About dialog and window centring (#14), large-PDF tree and XREF performance (#6), the diff depth-limit and multi-stream page fixes (#7), the decompression ceiling (#10, #13), the dump stream --json / --ops fixes (#4), and decoded metadata and attachment names.

Technical changes

1. ## [Unreleased] becomes ## [0.5.0] - 2026-10-14, with a one-line summary under it like the earlier releases.
2. Three entries under Added, four under Changed and five under Fixed for the changes listed above. The existing entries are unchanged.
3. A [0.5.0] compare link, v0.4.0...v0.5.0, at the bottom.

Considerations

The Wails alpha2.117 bump (#5) is already covered by the existing beta.18 entry, and the comment and test-naming cleanups (#1, #2, #8, #9, #11) have no user-visible effect, so they get no entry.

How was this tested?

• go test ./cmd/cli -run Doc and tests/naming-and-comment-hygiene, the two suites that read CHANGELOG.md, pass.
• The new entries are written from each PR's description (and the commit message for the metadata change), not re-checked against the code.

What could go wrong?

The heading is dated 2026-10-14, the planned tag date. If the tag goes out on another day, the heading needs the same change.

Screenshots/videos (if appropriate)

Checklist

• Tests pass locally
• I targeted the dev branch, not master

[unidoc-anom]

@anovik sorry, could you review this again as I adjust the release date