Fix RSS and Atom feeds returning 404 on static deployment

[Copilot]

The RSS/Atom feed routes (/feed.rss, /feed.atom, /dotnet_feed.rss, /dotnet_feed.atom) were never included in the static output because crawlLinks does not follow non-HTML link extensions during prerendering.

Change

• Explicitly added all four feed routes to nitro.prerender.routes in nuxt.config.ts

// nuxt.config.ts
nitro: {
  prerender: {
    routes: ['/', '/feed.rss', '/feed.atom', '/dotnet_feed.rss', '/dotnet_feed.atom'],
    crawlLinks: true,
    failOnError: false
  }
}

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• api.fontshare.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/techwatching.dev/techwatching.dev/node_modules/.bin/nuxt build (dns block)
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/techwatching.dev/techwatching.dev/node_modules/.bin/nuxt generate (dns block)
• api.fontsource.org
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/techwatching.dev/techwatching.dev/node_modules/.bin/nuxt build (dns block)
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/techwatching.dev/techwatching.dev/node_modules/.bin/nuxt generate (dns block)
• api.iconify.design
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/techwatching.dev/techwatching.dev/node_modules/.bin/nuxt build (dns block)
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/techwatching.dev/techwatching.dev/node_modules/.bin/nuxt generate (dns block)
• fonts.bunny.net
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/techwatching.dev/techwatching.dev/node_modules/.bin/nuxt build (dns block)
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/techwatching.dev/techwatching.dev/node_modules/.bin/nuxt generate (dns block)
• fonts.google.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/techwatching.dev/techwatching.dev/node_modules/.bin/nuxt build (dns block)
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/techwatching.dev/techwatching.dev/node_modules/.bin/nuxt generate (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>RSS feeds are returning 404</issue_title>
<issue_description>On page https://techwatching.dev/posts there is a link to RSS feed and atom feeds. Both are returning 404.
https://techwatching.dev/feed.rss
https://techwatching.dev/feed.atom

Probably a regression after migration.</issue_description>

<agent_instructions>Please fix this issue. Both feeds should work.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes RSS feeds are returning 404 #119

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull request overview

This PR fixes 404s for RSS/Atom feeds on static deployments by ensuring the feed endpoints are explicitly included in Nitro’s prerender route list (since link crawling won’t discover non-HTML extensions).

Changes:

• Add /feed.rss, /feed.atom, /dotnet_feed.rss, and /dotnet_feed.atom to nitro.prerender.routes in nuxt.config.ts.