Extensions
Nightly Builds
Just like DuckDB itself, DuckDB's core extensions have nightly or dev builds that can be used to try out features before they are officially released.
This can be useful when your workflow depends on a new feature, or when you need to confirm that your stack is compatible with the upcoming version.  
Nightly builds for extensions are slightly complicated due to the fact that currently DuckDB extensions binaries are tightly bound to a single DuckDB version. Because of this tight connection,
there is a potential risk for a combinatory explosion. Therefore, not all combinations of nightly extension build and nightly DuckDB build are available.  
In general, there are 2 ways of using nightly builds: using a nightly DuckDB build and using a stable DuckDB build. Let's go over the differences between the two:  
#### From Stable DuckDB {#docs:extensions:versioning_of_extensions::from-stable-duckdb}  
In most cases, user's will be interested in a nightly build of a specific extension, but don't necessarily want to switch to using the nightly build of DuckDB itself. This allows using a specific bleeding-edge
feature while limiting the exposure to unstable code.  
To achieve this, Core Extensions tend to regularly push builds to the [`core_nightly` repository](#docs:extensions:working_with_extensions::extension-repositories). Let's look at an example:  
First we install a [**stable DuckDB build**](https://duckdb.org/docs/installation/index.html).  
Then we can install and load a **nightly** extension like this:  
```sql
INSTALL aws FROM core_nightly;
LOAD aws;
```  
In this example we are using the latest **nightly** build of the aws extension with the latest **stable** version of DuckDB.  
#### From Nightly DuckDB {#docs:extensions:versioning_of_extensions::from-nightly-duckdb}  
When DuckDB CI produces a nightly binary of DuckDB itself, the binaries are distributed with a set of extensions that are pinned at a specific version. This extension version will be tested for that specific build of DuckDB, but might not be the latest dev build. Let's look at an example:  
First, we install a [**nightly DuckDB build**](https://duckdb.org/docs/installation/index.html). Then, we can install and load the `aws` extension as expected:  
```sql
INSTALL aws;
LOAD aws;
```