docs: add 0.2.0 changelog for lock-order and parity work - #144
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe changelog adds a dated 0.2.0 release section describing documentation, testing, search, caching, API, and export changes, and updates the Unreleased and 0.2.0 comparison links. ChangesRelease documentation
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
wpak-ai
left a comment
There was a problem hiding this comment.
document the user-facing changes shipped since v0.1.0 in the [0.2.0] section, not only the three internal PRs #138–#140 (eleven user-visible changes, #104, #105, #107, #108, #111, #120, #121, #122, #125, #127, #134, merged after v0.1.0 and were never recorded in [Unreleased] or [0.1.0], so tagging v0.2.0 with only three internal items leaves them with no release section to belong to and omits them from the Release notes that is-12 copies out of this section)
Expanded [0.2.0] to cover all eleven user-facing PRs since v0.1.0 |
Closes #141
Docs-only. Adds a [0.2.0] section to CHANGELOG.md for the Week 30 work in #138, #139, and #140: the search-index lock-order doc, the concurrency suite, and the Python/JS parity oracles. Clears [Unreleased] and updates the footer compare links. No version bump here; that lands in the release PR.
git diff --stat should show only CHANGELOG.md.
Summary by CodeRabbit