fix(feed): stop putting agent name in <author>, use <category> instead - #72
Merged
royalpinto007 merged 1 commit intoAug 7, 2026
Conversation
RSS 2.0's <author> element must contain an email address per spec, and feed validators/strict readers reject or mangle a bare name there. The agent is also the subject of the case, not the item's author, so <category> is the correct element for it. Escapes the agent name the same way title/desc already are, since names can contain '&'.
|
Nice work @waterlemonnn, this is merged. Contributions like this are what keep agentpostmortem moving. A star on the repo would mean a lot if this project is useful to you. Happy to see more from you whenever you have the time. |
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
2 participants
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.
Closes #56.
<author>in RSS 2.0 must contain an email address — a bare agent name there is invalid RSS and gets dropped or mangled by strict readers/validators. The agent is also the subject of the case rather than the author of the item, so<category>is the right fit, as suggested in the issue.<author>${agent?.name ?? "Unknown Agent"}</author><category>${agentName}</category>instead&/</>replace chain already used fortitleanddesc, since agent names can contain&(e.g.Microsoft / GitHub)Ran
npx prettier --check .,npm run lint,npx tsc --noEmit, andnpx vitest run(87/87 passing) — all clean.npm run buildcompiles and type-checks fine; it does fail later at the "Collecting page data" step, but that's/api/admin/posts/[id]/resend-tokenthrowing on a missingRESEND_API_KEYin my local env, unrelated to this route or change.