Remove the Firebase action integration

.gitignore

@@ -2,3 +2,4 @@ _site
 .sass-cache
 .jekyll-metadata
 .bundle
+.jekyll-cache

_data/integrations.yml

@@ -1,9 +1,3 @@
-- name: "Firebase Action"
-  id: "action-firebase"
-  image: "/assets/images/integrations/firebase.svg"
-  description: "Deploy sites to Firebase using GitHub actions."
-  labels: ["ACTION"]
-
 - name: "Slack ChatOps"
   id: "chatops"
   image: "/assets/images/integrations/slack.svg"

_includes/integrations.html

@@ -14,10 +14,6 @@ <h4 class="h4-mktg">Kubernetes</h4>
       <img src="/assets/images/integrations/github.svg" width="64px" height="64px">
       <h4 class="h4-mktg">GitHub Actions</h4>
     </div>
-    <div class="text-center p-3">
-      <img src="/assets/images/integrations/firebase.svg" width="64px" height="64px">
-      <h4 class="h4-mktg">Firebase</h4>
-    </div>
     <div class="text-center p-3">
       <img src="/assets/images/integrations/aws.svg" width="64px" height="64px">
       <h4 class="h4-mktg">AWS</h4>

_posts/2026-10-11-deliverybot-is-back.md

@@ -19,9 +19,8 @@ back at [app.deliverybot.dev]({{ site.deliverybot_url }}).
 The [codebase]({{ site.source_url }}) has been brought up to date:
 
 - It runs on Node.js 22 and the latest Probot.
-- Data, sessions and background jobs now live in PostgreSQL instead of
-  Firebase, and sessions are stored server-side with the GitHub token
-  encrypted.
+- Data, sessions and background jobs live in PostgreSQL, and sessions are
+  stored server-side with the GitHub token encrypted.
 - It ships as a container image with Kubernetes manifests, so it is easy to
   [run yourself](/docs/deploying/) too.