Skip to content

Tags

Tags

v0.1.3

Toggle v0.1.3's commit message
0.1.3: a feed over the byte cap is repaired at its last complete item

changelog.com/podcast/feed is 6.3 MB. At the 5 MiB cap the document was cut
mid-item, the parser threw, and the resolver moved on to the site's combined
feed, so the show page listed the wrong feed even with the path preference
from 0.1.2. The cap is 16 MiB now, safeFetch says when it bit, and a cut
RSS, Atom or RDF document is closed at its last complete item before parsing.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014JGnonZiv2TP3aSiu4LLWZ

v0.1.2

Toggle v0.1.2's commit message
0.1.2: prefer the advertised feed under the submitted page's path

Submitting changelog.com/podcast on p0dcasters listed changelog.com/feed,
the site-wide feed, because the show page advertises it first in the head
and findFeedLinks keeps document order. Advertised links under the page's
own path now go first, in their original order; the rest follow.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014JGnonZiv2TP3aSiu4LLWZ

v0.1.1

Toggle v0.1.1's commit message
0.1.1: keep node:dns out of the core entry

isPublicHost reached node:dns through a dynamic import inside net.js, which
core.js re-exported from, so a client bundle that imported the core entry
failed to build under webpack (p0dcasters' SubmitForm). The DNS half now
lives in resolve.js, the node-only entry; core keeps the pure address checks.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014JGnonZiv2TP3aSiu4LLWZ

v0.1.0

Toggle v0.1.0's commit message
submit-feed 0.1.0: the shared feed submission module and contract

Extracted from rssamplifier.com's packages/feed and ingest, and the
submit_feed MCP tool, so p0dcasters.com and any later directory take feeds
the same way: normalise and gate the URL, refuse private addresses on the
name and the redirect, discover the feed behind a site, parse RSS/Atom/JSON
Feed at channel level, read OPML, and answer with one reply shape.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014JGnonZiv2TP3aSiu4LLWZ