fix: remove changelog about unreleased tag

[rindrics]

• Release for v0.7.0 #127 did not work correctly 🤔

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

Review Summary by Qodo

Remove unreleased v0.7.0 changelog entry

🐞 Bug fix

Walkthroughs

Description

• Remove unreleased v0.7.0 changelog entry
• Revert incomplete changelog from previous PR attempt

Diagram

flowchart LR
  A["CHANGELOG.md<br/>with v0.7.0 entry"] -- "Remove unreleased<br/>v0.7.0 section" --> B["CHANGELOG.md<br/>starting with v0.6.0"]

Loading

File Changes

1. CHANGELOG.md 🐞 Bug fix +0/-6

Remove unreleased v0.7.0 changelog section

• Removed entire v0.7.0 changelog section (6 lines)
• Deleted unreleased version entry with 4 associated features/fixes
• Kept v0.6.0 and earlier versions intact

CHANGELOG.md

---

[coderabbitai]

Warning

Rate limit exceeded

@Rindrics has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 23 minutes and 35 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

Visit the preview URL for this PR (updated for commit 08c940b):

https://izuminokami-kanesada--pr135-fix-21x26fmi.web.app

_{(expires Fri, 20 Feb 2026 03:36:51 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 4c4412227845b968bcb4c8b6996048cdd07fd6de}

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

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Changelog/version mismatch 🐞 Bug ⛯ Reliability

Description

This PR removes the v0.7.0 section from CHANGELOG.md, leaving v0.6.0 as the latest entry while
package.json still declares version 0.7.0. This inconsistency can confuse users and may lead to
missing/incorrect release notes since tagpr is configured to source the release version from
package.json.

Code

CHANGELOG.md[R1-5]

# Changelog

-## [v0.7.0](https://github.com/Rindrics/izuminokami-kanesada/compare/v0.6.0...v0.7.0) - 2026-02-12
-- feat: provide copy button by @Rindrics in https://github.com/Rindrics/izuminokami-kanesada/pull/126
-- fix: improve appearance of prev/next button by @Rindrics in https://github.com/Rindrics/izuminokami-kanesada/pull/131
-- feat: provide collection functionality by @Rindrics in https://github.com/Rindrics/izuminokami-kanesada/pull/128
-- feat: add lunyu contents by @Rindrics in https://github.com/Rindrics/izuminokami-kanesada/pull/130
-
## [v0.6.0](https://github.com/Rindrics/izuminokami-kanesada/compare/v0.5.0...v0.6.0) - 2026-02-06
- feat: improve nav UI by @Rindrics in https://github.com/Rindrics/izuminokami-kanesada/pull/120
- feat(mcp): improve content generation workflow with MCP by @Rindrics in https://github.com/Rindrics/izuminokami-kanesada/pull/122

Evidence

CHANGELOG.md now starts with v0.6.0 as the latest entry, while package.json declares version 0.7.0;
additionally, tagpr is configured to read the version from package.json, so the release/tag version
source is now out of sync with the changelog.

CHANGELOG.md[1-5]
package.json[1-6]
.tagpr[4-8]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`CHANGELOG.md` no longer includes an entry for `v0.7.0`, but `package.json` still declares version `0.7.0`. Since tagpr is configured to read the release version from `package.json`, this can create release/tag events without matching changelog notes and causes user-facing confusion.

### Issue Context
This PR explicitly removes the `v0.7.0` changelog entry (“unreleased tag”), but it does not adjust the declared version.

### Fix Focus Areas
- CHANGELOG.md[1-5]
- package.json[1-6]
- .tagpr[4-8]

### Suggested fix approaches
1) Re-add a `v0.7.0` section (or move those bullets under an `Unreleased` section) so the changelog reflects the declared version, **or**
2) If `v0.7.0` is not released yet, revert `package.json` to `0.6.0` (or use a pre-release version) until the release is actually cut.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more

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

1. Changelog/version mismatch 🐞 Bug ⛯ Reliability

This PR removes the v0.7.0 section from CHANGELOG.md, leaving v0.6.0 as the latest entry while
package.json still declares version 0.7.0. This inconsistency can confuse users and may lead to
missing/incorrect release notes since tagpr is configured to source the release version from
package.json.

Agent Prompt

### Issue description
`CHANGELOG.md` no longer includes an entry for `v0.7.0`, but `package.json` still declares version `0.7.0`. Since tagpr is configured to read the release version from `package.json`, this can create release/tag events without matching changelog notes and causes user-facing confusion.

### Issue Context
This PR explicitly removes the `v0.7.0` changelog entry (“unreleased tag”), but it does not adjust the declared version.

### Fix Focus Areas
- CHANGELOG.md[1-5]
- package.json[1-6]
- .tagpr[4-8]

### Suggested fix approaches
1) Re-add a `v0.7.0` section (or move those bullets under an `Unreleased` section) so the changelog reflects the declared version, **or**
2) If `v0.7.0` is not released yet, revert `package.json` to `0.6.0` (or use a pre-release version) until the release is actually cut.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools