[JohnMcLear]

Adds the 3.3.14 entry to CHANGELOG.md so the release can go out.

Covers the fixes merged since v3.3.13 (#8423, #8425, #8409, #8410), credits the issue reporters and contributors, and adds a "Thanks to our security reporters" section linking each published advisory since mid-October. Test-only and dependabot changes are left out apart from a one-line dependency note.

The heading is # 3.3.14 on the first line, which is what bin/release.ts and bin/generateReleaseNotes.ts look for.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TcYAoEw35xr1qP19ipr25W

[qodo-code-review]

ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Document the 3.3.14 release

📝 Documentation 🕐 Less than 10 minutes

AI Description

• Adds 3.3.14 release notes covering startup, updater, collaboration, and history-mode fixes.
• Credits issue reporters, contributors, and security reporters with links to published advisories.
• Places the version heading first so release tooling can find the entry.

Diagram

graph TD
  A["CHANGELOG.md"] --> B["Release gate"] & C["Notes extractor"]

Loading

High-Level Assessment

Adding the entry to the existing changelog is the appropriate approach: both release scripts already consume that file, so a separate release-notes source would duplicate content without changing the release workflow.

Files changed (1) +28 / -0

Documentation (1) +28 / -0

CHANGELOG.mdAdd 3.3.14 release notes and acknowledgments +28/-0

Add 3.3.14 release notes and acknowledgments

• Prepends a 3.3.14 entry describing four areas of fixes and a brief dependency-update note. Credits fix reporters and contributors, and lists security reporters with links to their published advisories.

CHANGELOG.md

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. Security credits list advisories from earlier releases ✓ Resolved

Description

The 'Thanks to our security reporters' list in the new 3.3.14 section is described as covering
reports 'since mid-October', but it re-lists GHSA advisories already credited in the 3.3.3, 3.3.9,
3.3.11 and 3.3.12 entries (for example GHSA-35rj-7vrx-29wq for sun1024, GHSA-746x-9w89-7xv6 for
MaBeFHDW, GHSA-g9xm-3pqr-wcph for baeseungwon1010, GHSA-mc8w-wjhw-45x5 for gcm-explo1t,
GHSA-pp5v-mvwg-76mp for meifukun). Those advisories were published and fixed in earlier releases, so
the section mis-states its time window and repeats credits that were already given. Because this is
the public release note that goes out with the release, the wrong window and duplicate credits will
be published as-is.

---

Tip of the day

💡 Did you know, you can commit Qodo's fix in one click with committable suggestions (GitHub & GitLab)

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[JohnMcLear]

Thanks. The repeat is on purpose: this section thanks everyone whose advisory was published since mid-October, and those fixes went out in earlier releases. I've reworded the intro to say that (3.3.3 to 3.3.13) so it doesn't read as new reports.