v0.3.1 Release

[harumiWeb]

Summary by CodeRabbit

• New Features

  • SmartArt extraction via Excel with layout/name extraction and a compact hierarchical node payload (layout, nodes, kids)
  • Unified element classification introducing distinct Shape vs Arrow representations using a "kind" discriminator

• Documentation

  • Added v0.3.1 release notes and updated docs to reflect SmartArt and shape/arrow model and compatibility adjustments

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Bumps project version to 0.3.1, adds release notes for v0.3.1 describing SmartArt extraction and revised shape modeling (Shape, Arrow, SmartArt), updates documentation navigation, and updates README examples to introduce a kind discriminator and arrow-specific fields in serialized shape output.

Changes

Cohort / File(s)	Summary
Release notes & nav docs/release-notes/v0.3.1.md, mkdocs.yml	Add v0.3.1 release notes documenting SmartArt extraction via Excel COM and separate Shape/Arrow/SmartArt modeling; insert v0.3.1 into docs navigation.
Project metadata pyproject.toml	Bump project version from 0.3.0 to 0.3.1.
README & docs examples README.md, README.ja.md, docs/README.en.md, docs/README.ja.md	Update JSON examples to introduce a kind discriminator ("shape" / "arrow"), remove or change type usage for arrow entries, and add arrow-specific fields (begin_id, end_id, direction, arrow styles).
Release notes content docs/release-notes/v0.3.1.md	Documents compact SmartArt payload (layout, nodes, kids) and notes on changed field semantics (e.g., Shape.type scope, removed SmartArt fields).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• v0.2.80 #18 — related changes to connector/arrow representation and connector endpoint fields.
• Shapeのフローを追うために接続先/元を追加 #15 — overlaps with adding id, begin_id, end_id and connector handling.
• SmartArt解析構造化機能追加 #30 — implements SmartArt/Arrow types and refactors Shape/SmartArt/Arrow models and serializers.

Suggested labels

codex

Poem

🐰 A tiny hop, a doc unfurled,
SmartArt sketched from cells and swirls,
Shapes now wear a kinder name,
Arrows point where meanings aim,
Version nudged — 0.3.1 bounds forth with twirls.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'v0.3.1 Release' directly matches the main objective of the PR, which is to prepare and document the v0.3.1 release with version bumps, release notes, and updated documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f870f1e and 856ce03.

📒 Files selected for processing (4)

• README.ja.md
• README.md
• docs/README.en.md
• docs/README.ja.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Codacy Static Code Analysis
• GitHub Check: test (windows-latest, 3.12)

🔇 Additional comments (4)

docs/README.en.md (1)

219-246: Documentation changes look good.

The JSON examples clearly demonstrate the new kind discriminator introduced in v0.3.1. Shapes are properly tagged with "kind": "shape" alongside the existing "type" field, and arrows now use "kind": "arrow" without "type", while preserving connection metadata (begin_id, end_id, direction).

README.md (1)

5-5: Consistent with docs version; paths correctly adjusted for root-level location.

The JSON examples match docs/README.en.md, and asset paths are appropriately updated to /docs/... for this root-level README location.

Also applies to: 225-225, 233-233, 239-244, 164-164

docs/README.ja.md (1)

218-245: Japanese documentation maintains consistency with English version.

The JSON examples and kind discriminator changes are properly applied in the Japanese documentation, with relative paths correctly matching the file location.

README.ja.md (1)

5-5: Root-level Japanese README consistently updated with docs version.

All four documentation files (en/ja, root/docs) now coherently reflect the v0.3.1 shape/arrow model with the kind discriminator. Paths are correctly adjusted for file location in each case.

Also applies to: 224-224, 232-232, 238-244, 163-163

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!