GitHub Releases

Nuxt Content v3.16.1 introduces a new `content.llms` option to disable the `nuxt-llms` integration, enhancing flexibility for developers. Additionally, a security fix has been implemented to prevent ReDoS vulnerabilities in the `assertSafeQuery` function.

Nuxt Content v3.16.0 introduces several important bug fixes, including improved handling of git caches and stable async component identity in ContentRenderer. Additionally, it enhances date formatting to prevent timezone drift and ensures compatibility with trailing slashes in path-based lookups. Users may notice duplicate git caches, which can be safely removed without affecting functionality.

Nuxt Content v3.15.2 introduces important bug fixes, including the exclusion of temporary files in content source paths and enhanced security by rejecting SQL function calls in query WHERE clauses. These updates improve both development experience and application security.

Nuxt Content v3.15.1 includes a critical bug fix that preserves SQL hashes in HMR dumps, enhancing the development experience. This update addresses an issue reported by the community, ensuring better stability during hot module replacement.

Nuxt Content v3.15.0 introduces a new `bun` sqlite connector for Bun runtime deployments and enhances search functionality with type inference for extraFields. Bug fixes include improved validator detection with pnpm, better handling of file changes in collections, and adjustments to the search heading-level boost curve.

Nuxt Content v3.14.0 introduces the `useSearchCollection` composable for FTS5 full-text search, enhancing search capabilities. Additionally, custom properties have been added to ContentConfig and the SQLOperator type now supports NOT IN. Bug fixes include updates to documentation and improvements to slugify options and preview templates.

Nuxt Content v3.13.0 introduces important bug fixes, including a fix for unauthenticated SQL injection and adjustments to the `mdc:configSources` hook. Additionally, the `formatDate` and `formatDateTime` functions have been moved into the runtime subtree for better organization.