--- title: Announcing version history support for Cloud Firestore... description: Cloud Firestore Security Rules now support version history in the Firebase console. Developers can browse previously published rule versions, compare them... canonical: https://daily.dev/posts/announcing-version-history-support-for-cloud-firestore-security-rules-ouprtl8hp twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Announcing version history support for Cloud Firestore Security Rules | daily.dev og:description: Cloud Firestore Security Rules now support version history in the Firebase console. Developers can browse previously published rule versions, compare them... og:url: https://daily.dev/posts/announcing-version-history-support-for-cloud-firestore-security-rules-ouprtl8hp og:image: https://api.daily.dev/og/posts/oUPrtL8HP.png og:image:alt: Announcing version history support for Cloud Firestore Security Rules og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Announcing version history support for Cloud Firestore Security Rules **[Firebase](https://daily.dev/sources/firebase-blog)** · 2 min read · 0 upvotes · 0 comments ## Summary Cloud Firestore Security Rules now support version history in the Firebase console. Developers can browse previously published rule versions, compare them against the current version, view diffs, and roll back or mix rules from earlier versions. Every deploy that includes Rules creates a new version, and using `firebase deploy --only` from the CLI avoids cluttering history with unchanged rule deployments. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I roll back a bad Cloud Firestore security rule change? Use the version history feature in the Firebase console's Rules tab for Cloud Firestore. It lets you browse all previously published rule versions, compare any older version to the latest using the 'Compare to Latest' diff view, and edit the current version to fully roll back or mix in older rules. _daily.dev surfaces updates like this for teams managing Firestore security configurations._ ### Why does my Firestore rules version history show duplicate unchanged versions? Every deploy that includes Rules creates a new version entry, even if the rules content is unchanged, which happens when you deploy from the command line without excluding rules. Avoid this by running deploy commands like `firebase deploy --only functions` to deploy only the specific resources you changed, keeping rules version history clean. _Developers refining their Firebase CLI workflow often track tips like this on daily.dev._ ## Similar posts on daily.dev - [How to Create Role-Based Access Control \(RBAC\) with Custom Claims Using Firebase Rules](https://daily.dev/posts/how-to-create-role-based-access-control-rbac-with-custom-claims-using-firebase-rules-mfr8m0dds) · freeCodeCamp · 2 upvotes · 0 comments - [Testing Firestore security rules without touching production](https://daily.dev/posts/testing-firestore-security-rules-without-touching-production-hniqyzuq6) · All Things Open · 1 upvotes · 0 comments --- Tags: [#authentication](https://daily.dev/tags/authentication), [#firebase](https://daily.dev/tags/firebase) [View this post on daily.dev](https://daily.dev/posts/announcing-version-history-support-for-cloud-firestore-security-rules-ouprtl8hp) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Announcing version history support for Cloud Firestore Security Rules","url":"https://daily.dev/posts/announcing-version-history-support-for-cloud-firestore-security-rules-ouprtl8hp","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/announcing-version-history-support-for-cloud-firestore-security-rules-ouprtl8hp"},"datePublished":"2026-08-23T12:18:48.929Z","dateModified":"2026-08-24T06:51:40.349Z","description":"Cloud Firestore Security Rules now support version history in the Firebase console. Developers can browse previously published rule versions, compare them...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Firebase","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Firebase","logo":"https://media.daily.dev/image/upload/s--i395oqZH--/f_auto,q_auto/v1787487448/logos/firebase-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/firebase-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/announcing-version-history-support-for-cloud-firestore-security-rules-ouprtl8hp","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"authentication,firebase","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Firebase","item":"https://daily.dev/sources/firebase-blog"},{"@type":"ListItem","position":3,"name":"Announcing version history support for Cloud Firestore Security Rules"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/announcing-version-history-support-for-cloud-firestore-security-rules-ouprtl8hp#faq","mainEntity":[{"@type":"Question","name":"How do I roll back a bad Cloud Firestore security rule change?","acceptedAnswer":{"@type":"Answer","text":"Use the version history feature in the Firebase console's Rules tab for Cloud Firestore. It lets you browse all previously published rule versions, compare any older version to the latest using the 'Compare to Latest' diff view, and edit the current version to fully roll back or mix in older rules. daily.dev surfaces updates like this for teams managing Firestore security configurations."}},{"@type":"Question","name":"Why does my Firestore rules version history show duplicate unchanged versions?","acceptedAnswer":{"@type":"Answer","text":"Every deploy that includes Rules creates a new version entry, even if the rules content is unchanged, which happens when you deploy from the command line without excluding rules. Avoid this by running deploy commands like `firebase deploy --only functions` to deploy only the specific resources you changed, keeping rules version history clean. Developers refining their Firebase CLI workflow often track tips like this on daily.dev."}}]} ```