Skip to content

chore: release v0.2.2#350

Merged
bensonwong merged 1 commit intomainfrom
release/v0.2.2
Mar 17, 2026
Merged

chore: release v0.2.2#350
bensonwong merged 1 commit intomainfrom
release/v0.2.2

Conversation

@bensonwong
Copy link
Collaborator

Summary

  • Bump version 0.2.10.2.2
  • Add changelog entry for all changes since v0.2.1

Highlights

  • Breaking: Removed XML citation support (<cite> tags) — numeric [N] markers only
  • Added: CDN popover bundle, design token system, page-expand ghost transition, SDK version header
  • Fixed: Undefined markerMap keys, null/undefined verification indicator
  • Removed: ~2,000 lines of dead code, XML parser/normalizer

Test plan

  • Lint passes (216 files)
  • All 1,550 tests pass
  • Build succeeds (ESM, CJS, DTS, CDN bundle, Tailwind CSS)

🤖 Generated with Claude Code

Bump version to 0.2.2, add changelog entry covering XML citation
removal, CDN popover bundle, design tokens, page-expand ghost
transition, SDK version header, and dead code cleanup.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@claude
Copy link

claude bot commented Mar 17, 2026

PR Review

The diff itself is clean — minimal, well-scoped, and the changelog entry is thorough with good issue references and a documented migration path. One concern worth discussing before merging:

Semver: patch bump vs. minor bump

The changelog documents Breaking Changes — specifically, four public exports are removed:

  • normalizeCitations()
  • parseCitation()
  • replaceCitations()
  • ReplaceCitationsOptions

Per Semantic Versioning, removing a public API is a breaking change. For pre-1.0 packages the convention is to increment the minor version for breaking changes (→ 0.3.0), not the patch. Releasing this as 0.2.2 means any consumer running npm update or with "deepcitation": "^0.2.1" in their lockfile could silently pick up a build-breaking version.

Suggestion: Bump to 0.2.30.3.0 instead, or add a note in the PR / release notes explicitly calling out that ^0.2.1 ranges will receive this breaking change. This is especially relevant since the migration path (parseCitationResponse() / replaceCitationMarkers()) requires manual code changes.

Everything else looks good

  • Changelog structure follows Keep a Changelog conventions ✓
  • [Unreleased] and version comparison links are correctly updated ✓
  • Issue references (#337–#342, #349) are included ✓
  • Migration path is documented in the Breaking Changes section ✓
  • No logic changes — pure housekeeping commit ✓

The semver point is the only blocker worth discussing; happy to approve once that's addressed or consciously accepted.

@github-actions
Copy link
Contributor

✅ Playwright Test Report

Status: Tests passed

📊 Download Report & Snapshots (see Artifacts section)

What's in the Visual Snapshots

The gallery includes visual snapshots for:

  • 🖥️ Desktop showcase (all variants × all states)
  • 📱 Mobile showcase (iPhone SE viewport)
  • 📟 Tablet showcase (iPad viewport)
  • 🔍 Popover states (verified, partial, not found)
  • 🔗 URL citation variants

Run ID: 23186993590

@bensonwong bensonwong merged commit 99f5a32 into main Mar 17, 2026
9 checks passed
@bensonwong bensonwong deleted the release/v0.2.2 branch March 17, 2026 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant