cleanup and docs

docs/README.md

@@ -100,16 +100,6 @@ CLI:
 duckdb -unsigned
 ```
 
-Python:
-```python
-con = duckdb.connect(':memory:', config={'allow_unsigned_extensions' : 'true'})
-```
-
-NodeJS:
-```js
-db = new duckdb.Database(':memory:', {"allow_unsigned_extensions": "true"});
-```
-
 Secondly, you will need to set the repository endpoint in DuckDB to the HTTP url of your bucket + version of the extension 
 you want to install. To do this run the following SQL query in DuckDB:
 ```sql

docs/UPDATING.md

@@ -0,0 +1,12 @@
+# Extension updating 
+When cloning this template, the target version of DuckDB should be the latest stable release of DuckDB. However, there 
+will inevitably come a time when a new DuckDB is released and the extension repository needs updating. This process goes
+as follows:
+
+- Bump submodules
+  - `./duckdb` should be set to latest tagged release
+  - `./extension-ci-tools` should be set to updated branch corresponding to latest DuckDB release
+- Bump versions in `./github/workflows`
+  - `duckdb_version` input in `MainDistributionPipeline.yml` should be set to latest tagged release
+  - reusable workflow `_extension_distribution.yml` should be set to updated branch corresponding to latest DuckDB release
+

extension_config.cmake

@@ -6,5 +6,5 @@ duckdb_extension_load(quack
     LOAD_TESTS
 )
 
-# Any extra extensions
+# Any extra extensions that should be built
 # e.g.: duckdb_extension_load(json)