# DuckDB v0.8.1 — Release & Upgrade Intelligence
- **Product:** DuckDB (https://duckdb.org)
- **Version:** v0.8.1
- **Released:** Jun 13, 2023
- **Impact Score:** 5/10
- **Breaking Changes:** Not verified
- **Canonical Analysis:** https://changelogs.us/duckdb/updates/v0.8.1/

## Executive Summary (TL;DR)
DuckDB v0.8.1. Source highlight: This is a bug fix release for various issues discovered after we released 0.8.0. There are no new features, just bug fixes. Database files created by DuckDB v0.8.0 can be read by DuckDB v0.8.1 (i.e. v0.8.1 is backwards compatible with v0.8.0). Note that database files created by v0.8.1 cannot be rea

## New Features
- Add the default scheme to the CREATE TYPE's type search path.
- feat: introduce a common grammar/types file for libpgquery parser and update Python scripts to take source/target directory paths as argument
- Remove all C-style casts and add clang-tidy rule to forbid them
- Add missing entries to ParquetDecodeUtils::BITPACK_MASKS
- Implement #7662 - add the "lock_configuration" setting which allows configurations to be locked down
- Add FuzzyDuck fuzzer - and move fuzzer CI to separate repo

## Improvements
- Enhance the generation of random floating point by PCG

## Bug Fixes
- Fix #7582 - correctly set "last_offset" in InitializeScanWithOffset and turn assertion into run-time check
- Partially fix #7551 - throw internal exception in case of type mismatch in ExpressionExecutor
- Fix #7602 - allow reserved keywords in named parameters
- Fix #7599 - output a clear error message when a subquery is used in a table function that does not support it
- Fix #7564 - if the auto-complete extension is not enabled, inline it into the shell
- Fix sql auto complete extension CI issue