<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Webhooks on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/webhooks/</link><description>Recent content in Webhooks on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 30 Oct 2026 16:53:40 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/webhooks/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub webhook IP ranges added to Meta API hooks field</title><link>https://curadevops.metacog.co.kr/insights/2026-10-30-webhook-ip-ranges-added-to-the-meta-api/</link><pubDate>Fri, 30 Oct 2026 16:53:40 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-30-webhook-ip-ranges-added-to-the-meta-api/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> If your org maintains a firewall or security-group allowlist for incoming GitHub webhook traffic, update it to include the new IP ranges from the Meta API hooks field before deployments that rely on webhooks start failing.&lt;/li>
&lt;li>&lt;strong>CI/CD — Plan:&lt;/strong> Pipelines that trigger via GitHub webhooks and sit behind a strict inbound allowlist may silently drop deliveries; pull the updated ranges from the Meta API and refresh your allowlist rules.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>