Repository navigation
fix(notes): drop an entry's own refs from LLM-rewritten descriptions - #747
Merged
Merged
Conversation
Contributor
|
Standing release PR: #730 · v0.42.1 queued (4 packages) · open 40m · ✅ ready to merge Release Preview — v0.42.0 → v0.42.1
These changes will be added to the release PR (#730) when merged: Changelogmonorepo 0.42.0 → 0.42.1
After merge — predicted release
Updated automatically by ReleaseKit |
Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced Oct 23, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The model sometimes copies an entry's reference into its rewritten description. The built-in renderer strips it (
neutralizeDescriptionRefs), but templates print the description and then append the entry's refs, so #614's notes showed(#608) (#608).removeDescriptionRefs: removes the given refs from a description and leaves every other ref (and inline code) as written. Escaping and linking stay with the renderers.enhanceandenhance-and-categorizenow remove the entry's own refs (issueIdsandprNumber) from the description the model returns, so every renderer gets a clean description.Related Issue(s)
Closes #719
Type of Change
feat— New featurefix— Bug fixdocs— Documentation changerefactor— Code refactoringtest— Adding or updating testschore— Maintenance, dependencies, toolingScope
@releasekit/version@releasekit/notes@releasekit/publish@releasekit/release@releasekit/config@releasekit/coreChecklist
pnpm lint)pnpm test)pnpm typecheck)Testing Notes
enhanceAndCategorizewith a model reply whose description ends in the entry's own(#N).🤖 Generated with Claude Code


Confidence Score: 5/5
The PR appears safe to merge; no actionable defects were found.Summary
Removes an entry’s own issue and pull-request references from model-rewritten descriptions before renderers receive them.
Acknowledged follow-up: goosewobbler states that a notes-level regression test through
enhanceAndCategorizeis still to add.Reviews (1) · Last reviewed commit: "fix(notes): drop an entry's own refs fro..." · Reviewed by Greptile