<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SudarshanTechLabs Blog: Version Catalog</title>
    <link>https://sudarshantechlabs.com/blog/tag/version-catalog</link>
    <description>Posts tagged Version Catalog from SudarshanTechLabs.</description>
    <language>en-us</language>
    <lastBuildDate>Thu, 09 Jul 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://sudarshantechlabs.com/blog/tag/version-catalog/feed.xml" rel="self" type="application/rss+xml" />
    <managingEditor>support@sudarshantechlabs.com (Sudarshan Chaudhari)</managingEditor>
    <webMaster>support@sudarshantechlabs.com (Sudarshan Chaudhari)</webMaster>
    <item>
      <title>My Kotlin Gradle Build Setup With Version Catalogs</title>
      <link>https://sudarshantechlabs.com/blog/kotlin-gradle-build-setup-version-catalogs</link>
      <guid isPermaLink="true">https://sudarshantechlabs.com/blog/kotlin-gradle-build-setup-version-catalogs</guid>
      <description>Keeping Gradle sane across 20+ Android apps means one source of truth for versions. Here&apos;s how I use version catalogs, convention plugins, and a shared version file to stop dependency drift before it starts. · 4 min read</description>
      <pubDate>Thu, 09 Jul 2026 00:00:00 GMT</pubDate>
      <category>Gradle</category>
      <category>Kotlin</category>
      <category>Version Catalog</category>
      <category>Android</category>
      <category>Build</category>
      <enclosure url="https://sudarshantechlabs.com/og-image.png" type="image/png" length="0"/>
    </item>
  </channel>
</rss>