Enter your suggestions in details:

Sorry, possibly a bit of an edge case here... I just added https://nodejs.org/en/feed/vulnerability.xml to one of our company's Slack channels so we get pinged in-channel about new security updates.
So far so good. But apparently 30 minutes ago the new Node 18+20 builds were ready but the RSS didn't update to trigger Slack updates.

1. Follow https://nodejs.org/en/feed/vulnerability.xml
2. https://groups.google.com/g/nodejs-sec/c/m_wMICiQrlM says:
   • "The Node.js project will release new versions of all supported release lines on or shortly after Friday October 13 2023. For more information see: https://nodejs.org/en/blog/vulnerability/october-2023-security-releases"
   • "The planned security releases are now available. You can read more about the details in https://nodejs.org/en/blog/vulnerability/october-2023-security-releases."
3. Note that both URLs in the nodejs-sec Google Group point to the same page/post.
4. Not sure if RSS/Slack/Feedly is determining new content by a change to a guid or new link tag, but looks like neither changed when the new releases were available since the page was updated, not a new page.

   <link>https://nodejs.org/en/blog/vulnerability/october-2023-security-releases</link>
   <guid>/blog/vulnerability/october-2023-security-releases</guid>

I could instead follow https://nodejs.org/en/feed/releases.xml for new Node releases in our Slack RSS integration, but then that'd notify us on EVERY new release, not just sec-releases. Not sure if it's possible to modify the guid/link with some hash or timestamp to cause it to invalidate when the page is updated. 🙏