Bump astral-sh/setup-uv from 9.0.0 to 10.0.0 in the github-actions group

.github/workflows/pipeline.yml

@@ -129,7 +129,7 @@ jobs:
     steps:
       - uses: actions/checkout@v7.0.1
 
-      - uses: astral-sh/setup-uv@v9.0.0
+      - uses: astral-sh/setup-uv@v10.0.0
 
       - name: Configure git identity
         run: |

CHANGELOG/0.7.34.md

@@ -0,0 +1,15 @@
+# 0.7.34
+
+Fixes processing configurations that apply to more than one dataset only being picked up by whichever dataset the
+metadata API happened to list first.
+
+### Bug fixes
+
+- **Shared processing configs**: a data processing configuration can apply to several datasets through its
+  `appliesToDataset` list. `map_processing_config_item` only ever read the first entry in that list, so a shared
+  config was attached to one dataset and silently dropped for the others, and which dataset won depended on the
+  order the API returned.
+
+  `_build_processing_configs` now passes the requested dataset IDs down and maps the config once for each dataset in
+  `appliesToDataset` that was actually asked for, so every dataset gets its own copy regardless of ordering. A config
+  that applies to none of the requested datasets is logged as a warning and skipped.

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "dri-timeseries-processor"
-version = "0.7.33"
+version = "0.7.34"
 description = "Timeseries processor service."
 readme = "README.md"
 license = { file = "LICENSE" }