# Self-referential CHANGELOG links to this repo's own release tags and compares.
# A release PR cuts a new version section whose link refs point at
#   https://github.com/agentjp/bdinfo-rs/releases/tag/vX.Y.Z
#   https://github.com/agentjp/bdinfo-rs/compare/vX.Y.Z...HEAD
# Both 404 until the vX.Y.Z tag is pushed, which by our release flow happens
# after the PR merges -- so without these excludes the Check links gate hard-
# fails on every release or version-bump PR. We exclude only our own tag and
# compare URLs, so those PRs stay green with no per-PR step while lychee still
# verifies every other link, including the badges, /releases, and installer URLs.
# The optional `ai\.` matches the ai.github.com SSH-config host alias too: if a
# convco-generated link ever escapes the release-prep host-rewrite, lychee would
# fail to resolve ai.github.com AND the github.com-only exclude would miss it.
https://(ai\.)?github\.com/agentjp/bdinfo-rs/releases/tag/v
https://(ai\.)?github\.com/agentjp/bdinfo-rs/compare/v

# The npm package @bdinfo-rs/wasm IS published now (registry 200), but its
# npmjs.com PAGE returns 403 to automated clients (npm's anti-bot), so lychee
# cannot verify it regardless of publication -- a permanent exclusion, like other
# bot-walled hosts, NOT the earlier "404 until first release" reason.
https://www\.npmjs\.com/package/@bdinfo-rs/wasm
