energy_price_cap_levels_annex_9: Promoting changes to process new format (Oct-Dec 2026 release)

.github/PULL_REQUEST_TEMPLATE/prod_template.md

@@ -1,13 +1,31 @@
-## Dev → Prod Promotion Checklist
+<!-- PR template for promoting from dev to prod -->
+
+---
+
+## Description
 
-### Pipeline description
 <!-- Which pipeline(s) does this promote? What changed? -->
 
+## Type of promotion
+- [ ] Existing pipeline - code/data update
+- [ ] New pipeline - first promotion to prod
+
+## Instructions for reviewer
+
+<!-- Anything they should pay particular attention to -->
+
+## Checklist
+
 ### Pipeline run
-- [ ] Manual pipeline run completed successfully on dev after merging to dev
+- [ ] Manual pipeline run completed successfully on dev after merging to dev (link the run below)
 - [ ] Dev S3 output spot-checked; row counts and values look reasonable
 - [ ] No unexpected nulls or schema changes in output parquet files
 
+### Image freshness
+- [ ] `dev-latest` in ECR was rebuilt from the tip of `dev` that includes this PR's changes
+      (check the "Build and push Docker Image to ECR" run in Actions, as promotion only re-tags
+      the existing image, it doesn't rebuild)
+
 ### Code quality
 - [ ] run-tests workflow passed on this PR
 - [ ] No hardcoded credentials or environment-specific values
@@ -17,5 +35,9 @@
 - [ ] No changes to silver/gold dataset column names or types that would break Superset
       <!-- If there are column/type changes, describe them here and provide instructions on changes needed in Superset -->
 
-### Notes
+### After merging
+- [ ] Trigger the "Run pipeline in prod" workflow to actually refresh prod data — merging this
+      PR only re-tags the image, it does not run the pipeline. Requires approval from at least one of named CODEOWNERS.
+
+## Notes
 <!-- Any context the approver should know before merging -->

.github/pull_request_template.md

@@ -0,0 +1,31 @@
+<!-- PR template for merges to dev -->
+
+---
+
+## Description
+
+<!-- What does this change, and why? -->
+
+Fixes # <!-- Issue number -->
+
+## Type of change
+
+- [ ] New pipeline
+- [ ] Change to an existing pipeline
+- [ ] Package / infrastructure change
+- [ ] Docs only
+
+## Checklist
+
+- [ ] `uv run pytest` passes locally
+- [ ] `uv run pre-commit run --all-files` passes (ruff, gitleaks, etc.)
+- [ ] If this adds a new pipeline: it's registered in `pipelines.yaml` and has its own `README.md`
+- [ ] I've merged the latest `dev` into this branch
+
+## Testing notes
+
+<!-- How did you verify this works? e.g. ran locally with `--stage all`, ran via the "Test pipeline in dev" GitHub Actions workflow -->
+
+## Instructions for reviewer
+
+<!-- Anything they should pay particular attention to -->

.gitignore

@@ -49,6 +49,11 @@ infrastructure/.env
 *.parquet
 /data/
 
+# Notebooks
+# Scratch notebooks aren't meant to be committed — see docs/DEVELOPMENT.md
+*.ipynb
+.ipynb_checkpoints/
+
 # Logs
 *.log
 

.pre-commit-config.yaml

@@ -21,7 +21,7 @@ repos:
 
     ### Python Tools ###
 -   repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.15.20
+    rev: v0.16.4
     hooks:
     -   id: ruff-check
         args: [--fix]
@@ -30,15 +30,15 @@ repos:
         name: "🐍 python · Format with Ruff"
 
 -   repo: https://github.com/abravalheri/validate-pyproject
-    rev: v0.25
+    rev: '0.26'
     hooks:
     -   id: validate-pyproject
         name: "🐍 python · Validate pyproject.toml"
         additional_dependencies: ["validate-pyproject-schema-store[all]"]
 
     ### Data & Config Validation ###
 -   repo: https://github.com/python-jsonschema/check-jsonschema
-    rev: 0.37.4
+    rev: 0.38.0
     hooks:
     -   id: check-github-workflows
         name: "🐙 github-actions · Validate gh workflow files"