docs: update CHANGELOG.md for 0.2.2

[jorben]

Auto-generated changelog update for release 0.2.2.
Comparing changes from 0.2.1 to 0.2.2.

This PR was automatically created by the changelog workflow.

[github-actions]

Summary

This PR adds a changelog entry for version 0.2.2 documenting a Windows code signature verification fix. However, there's a critical missing element: the comparison link [0.2.2] at the bottom of the file is absent, which breaks the "compare" links in the changelog. Additionally, both 0.2.1 and 0.2.2 share the same date (2026-02-14), which seems unintentional.

Critical

• CHANGELOG.md:121 — Missing version comparison link for 0.2.2: The new version 0.2.2 has no corresponding comparison link at the bottom of the file. All other versions (0.1.8, 0.2.0, 0.2.1) have [version]: https://github.com/.../compare/... links. Add [0.2.2]: https://github.com/MarkPDFdown/markpdfdown-desktop/compare/0.2.1...0.2.2 at the bottom to match the existing pattern.

Important

• CHANGELOG.md:6 — Duplicate dates for sequential releases: Both 0.2.1 and 0.2.2 are dated 2026-02-14. If 0.2.1 was released earlier in the day, consider using a different date (e.g., 2026-02-15) or clarify in the description that these were released on the same day.

Suggestion

• CHANGELOG.md:9 — PR reference in commit message: The entry already includes the PR reference PR [#42] in parentheses, which is good. However, the commit hash link also points to PR #42. Consider simplifying to avoid redundancy, e.g., - **build**: 📦 disable code signature verification for Windows updates (by @jorben) since the commit hash already links to the PR.

Praise

• CHANGELOG.md:6-9 — Proper Keep a Changelog format: The new entry correctly uses the ## [version] - date header, ### :bug: Bug Fixes category, and includes the commit hash, PR reference, and contributor attribution. This follows the project's chosen changelog convention well.