Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 0 additions & 6 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,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
Comment on lines 1 to 5

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

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

Expand Down