changelog: move #67807 entry to Fixes section#68509
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 33d9c90a4d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ### Fixes | ||
|
|
||
| - Cron/delivery: clean up isolated sessions after direct deliveries when `deleteAfterRun` is enabled, covering structured and threaded branches that previously bypassed cleanup. (#67807) Thanks @MonkeyLeeT. |
There was a problem hiding this comment.
Append moved changelog fix entry to section tail
This relocates #67807 to the top of ### Fixes, but the repository rule in AGENTS.md says to "append new entries to the end of the target section" and not insert at the top; placing it first violates the changelog ordering policy and makes the unreleased fix list inconsistent with the project’s required maintenance flow.
Useful? React with 👍 / 👎.
Greptile SummaryCorrectly recategorizes the Confidence Score: 5/5Safe to merge; the only finding is a P2 ordering guideline violation in the changelog. All findings are P2 (style/placement); no code is affected. The recategorization and prefix rewording are correct. CHANGELOG.md — entry position within the Fixes section. Prompt To Fix All With AIThis is a comment left during a code review.
Path: CHANGELOG.md
Line: 13
Comment:
**Entry appended to section top instead of end**
CLAUDE.md requires: "in the active version block, append new entries to the end of the target section (`### Changes` or `### Fixes`); do not insert new entries at the top of a section." The `#67807` entry landed at line 13 — the very first position in `### Fixes` — rather than at the end (currently line 54, after the `Agents/failover` entry).
(The fix is to cut this line and paste it after line 54, just before the blank line separating the `## 2026.4.15` block.)
**Context Used:** CLAUDE.md ([source](https://app.greptile.com/review/custom-context?memory=fd949e91-5c3a-4ab5-90a1-cbe184fd6ce8))
How can I resolve this? If you propose a fix, please make it concise.Reviews (1): Last reviewed commit: "changelog: move #67807 entry to Fixes se..." | Re-trigger Greptile |
|
|
||
| ### Fixes | ||
|
|
||
| - Cron/delivery: clean up isolated sessions after direct deliveries when `deleteAfterRun` is enabled, covering structured and threaded branches that previously bypassed cleanup. (#67807) Thanks @MonkeyLeeT. |
There was a problem hiding this comment.
CLAUDE.md requires: "in the active version block, append new entries to the end of the target section (### Changes or ### Fixes); do not insert new entries at the top of a section." The #67807 entry landed at line 13 — the very first position in ### Fixes — rather than at the end (currently line 54, after the Agents/failover entry).
(The fix is to cut this line and paste it after line 54, just before the blank line separating the ## 2026.4.15 block.)
Context Used: CLAUDE.md (source)
Prompt To Fix With AI
This is a comment left during a code review.
Path: CHANGELOG.md
Line: 13
Comment:
**Entry appended to section top instead of end**
CLAUDE.md requires: "in the active version block, append new entries to the end of the target section (`### Changes` or `### Fixes`); do not insert new entries at the top of a section." The `#67807` entry landed at line 13 — the very first position in `### Fixes` — rather than at the end (currently line 54, after the `Agents/failover` entry).
(The fix is to cut this line and paste it after line 54, just before the blank line separating the `## 2026.4.15` block.)
**Context Used:** CLAUDE.md ([source](https://app.greptile.com/review/custom-context?memory=fd949e91-5c3a-4ab5-90a1-cbe184fd6ce8))
How can I resolve this? If you propose a fix, please make it concise.* changelog: move openclaw#67807 entry to Fixes section * changelog: move openclaw#67807 entry to Fixes section with correct PR-number ordering
* changelog: move openclaw#67807 entry to Fixes section * changelog: move openclaw#67807 entry to Fixes section with correct PR-number ordering
* changelog: move openclaw#67807 entry to Fixes section * changelog: move openclaw#67807 entry to Fixes section with correct PR-number ordering
* changelog: move openclaw#67807 entry to Fixes section * changelog: move openclaw#67807 entry to Fixes section with correct PR-number ordering
* changelog: move openclaw#67807 entry to Fixes section * changelog: move openclaw#67807 entry to Fixes section with correct PR-number ordering
Summary
#67807changelog entry from### Changesto### Fixes, since it is a bug fixCron/delivery:prefix consistent with other entries in the Fixes section