optimizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.15 Package lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 in Conan 2 have been greatly simplified and made way more flexible. Lockfiles are now modeled as lists of sorted references, which allow one single lockfile being used for multiple configurations, merging system integration like CMakeToolchain). This new configuration system can define strings, boolean, lists, being cleaner, more structured and powerful than using environment variables. A better, more explicit

optimizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.15 Package lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 in Conan 2 have been greatly simplified and made way more flexible. Lockfiles are now modeled as lists of sorted references, which allow one single lockfile being used for multiple configurations, merging system integration like CMakeToolchain). This new configuration system can define strings, boolean, lists, being cleaner, more structured and powerful than using environment variables. A better, more explicit

optimizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.15 Package lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 in Conan 2 have been greatly simplified and made way more flexible. Lockfiles are now modeled as lists of sorted references, which allow one single lockfile being used for multiple configurations, merging system integration like CMakeToolchain). This new configuration system can define strings, boolean, lists, being cleaner, more structured and powerful than using environment variables. A better, more explicit

optimizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.15 Package lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 in Conan 2 have been greatly simplified and made way more flexible. Lockfiles are now modeled as lists of sorted references, which allow one single lockfile being used for multiple configurations, merging system integration like CMakeToolchain). This new configuration system can define strings, boolean, lists, being cleaner, more structured and powerful than using environment variables. A better, more explicit

optimizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.15 Package lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 in Conan 2 have been greatly simplified and made way more flexible. Lockfiles are now modeled as lists of sorted references, which allow one single lockfile being used for multiple configurations, merging system integration like CMakeToolchain). This new configuration system can define strings, boolean, lists, being cleaner, more structured and powerful than using environment variables. A better, more explicit

· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 1547 9.3.3 View component metrics· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 1548 9.4 tuziemon (First-time contributor) • xyproto (First-time contributor) 2.3 TiDB Features This document lists the features supported in different TiDB versions, including Long- Term Support (LTS) versions and configuration item. 2.5.8 Limitations on TiKV version In your cluster, if the version of the TiDB component is v6.2.0 or later, the version of TiKV must be v6.2.0 or later. 2.6 Credits Each contributor

· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 1248 9.3.3 View component metrics· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 1249 9.4 tuziemon (First-time contributor) • xyproto (First-time contributor) 2.3 TiDB Features This document lists the features supported in different TiDB versions, including Long- Term Support (LTS) versions and configuration item. 2.5.8 Limitations on TiKV version In your cluster, if the version of the TiDB component is v6.2.0 or later, the version of TiKV must be v6.2.0 or later. 2.6 Credits Each contributor

· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 1154 9.3.3 View component metrics· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 1155 9.4 TiDB Release Notes PDF to view all release notes between the two LTS versions. The following table lists some highlights from 7.6.0 to 8.1.0: Category Feature/Enhancement Description Change type Description TiCDC security �→ . �→ client �→ - �→ allowed �→ - �→ user Newly added Lists the user- names that are allowed for client authenti- cation. Authen- tication requests with user-

· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 1157 9.3.3 View component metrics· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 1158 9.4 supports multiple load balancing policies #465 @djshow832 @xhebox TiProxy is the official proxy component of TiDB, located between the client and TiDB server. It provides load balancing and connection persistence contributor) • tonyxuqqi • wwu (First-time contributor) • yzhan1 2.3 TiDB Features This document lists the features supported in different TiDB versions, including Long- Term Support (LTS) versions and

· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 1162 9.3.3 View component metrics· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 1163 9.4 3.0, when using primary-secondary mode for high availability, TiProxy re- quires an additional component to manage the virtual IP address. Starting from v8.3.0, TiProxy supports built-in virtual IP management michaelmdeng • mittalrishabh • qingfeng777 • SandeepPadhi • yzhan1 2.3 TiDB Features This document lists the features supported in different TiDB versions, including Long- Term Support (LTS) versions and