From 8dd02171caca713169d342a390ed46b2239893b9 Mon Sep 17 00:00:00 2001
From: shiny-code-bot <332303085+shiny-code-app[bot]@users.noreply.github.com>
Date: Sun, 8 Nov 2026 00:56:22 -0500
Subject: [PATCH 1/2] Update shared-addons exact pins for Odoo 20 consumers

---
 docs/tooling/renovate.md |  7 +++++++
 renovate/devkit-pin.json | 19 ++++++++++++++++++-
 2 files changed, 25 insertions(+), 1 deletion(-)

diff --git a/docs/tooling/renovate.md b/docs/tooling/renovate.md
index 124aa65..ba1e2ee 100644
--- a/docs/tooling/renovate.md
+++ b/docs/tooling/renovate.md
@@ -20,6 +20,13 @@ Renovate opens a pull request for each alert it can fix.
   consumer's exact odoo-devkit pins, in `workspace.toml` and in workflow
   `uses:` references, to the head commit of devkit `main`
   ([build-tool upgrades](build-tool-upgrades.md#moving-the-pin)).
+  It also moves `[repos.shared_addons].ref` to shared-addons `main` as an
+  exact commit when `[build].odoo_version` is `20.0` and the repository is
+  `cbusillo/odoo-shared-addons`. Renovate reads the consumer's base branch
+  manifest, so landing its Odoo 20 conversion activates these updates; an
+  unmerged conversion does not. Odoo 19 shared-addons pins stay unchanged.
+  Shared-addons updates use ordinary visible pull requests, preview checks
+  and the merge train. Production still requires Client release acceptance.
 
 ## Repository Config
 
diff --git a/renovate/devkit-pin.json b/renovate/devkit-pin.json
index 5ae4e56..5514c2b 100644
--- a/renovate/devkit-pin.json
+++ b/renovate/devkit-pin.json
@@ -1,6 +1,6 @@
 {
   "$schema": "https://docs.renovatebot.com/renovate-schema.json",
-  "description": "Moves a consumer's exact odoo-devkit pins to devkit main's head commit (cbusillo/odoo-devkit#248).",
+  "description": "Moves exact devkit pins and Odoo 20 shared-addons pins to their main head commits.",
   "customManagers": [
     {
       "customType": "regex",
@@ -21,6 +21,17 @@
       "currentValueTemplate": "main",
       "packageNameTemplate": "https://github.com/{{{depName}}}",
       "datasourceTemplate": "git-refs"
+    },
+    {
+      "customType": "jsonata",
+      "fileFormat": "toml",
+      "managerFilePatterns": ["/^workspace\\.toml$/"],
+      "matchStrings": [
+        "$[build.odoo_version = '20.0'].repos.shared_addons[repository = 'cbusillo/odoo-shared-addons' and $exists(ref) and $contains(ref, /^[0-9a-f]{40}$/)].{'depName': repository, 'currentDigest': ref}"
+      ],
+      "currentValueTemplate": "main",
+      "packageNameTemplate": "https://github.com/{{{depName}}}",
+      "datasourceTemplate": "git-refs"
     }
   ],
   "packageRules": [
@@ -29,6 +40,12 @@
       "matchDepNames": ["cbusillo/odoo-devkit"],
       "commitMessageTopic": "odoo-devkit pin",
       "schedule": ["at any time"]
+    },
+    {
+      "matchManagers": ["custom.jsonata"],
+      "matchDepNames": ["cbusillo/odoo-shared-addons"],
+      "commitMessageTopic": "shared-addons pin",
+      "schedule": ["at any time"]
     }
   ]
 }

From 80312840f804f477a59405db5c7b28072e5a8533 Mon Sep 17 00:00:00 2001
From: shiny-code-bot <332303085+shiny-code-app[bot]@users.noreply.github.com>
Date: Sun, 8 Nov 2026 00:58:52 -0500
Subject: [PATCH 2/2] Clarify that shared-addons updates keep existing exact
 pins

---
 docs/tooling/renovate.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/tooling/renovate.md b/docs/tooling/renovate.md
index ba1e2ee..a20ab78 100644
--- a/docs/tooling/renovate.md
+++ b/docs/tooling/renovate.md
@@ -20,9 +20,9 @@ Renovate opens a pull request for each alert it can fix.
   consumer's exact odoo-devkit pins, in `workspace.toml` and in workflow
   `uses:` references, to the head commit of devkit `main`
   ([build-tool upgrades](build-tool-upgrades.md#moving-the-pin)).
-  It also moves `[repos.shared_addons].ref` to shared-addons `main` as an
-  exact commit when `[build].odoo_version` is `20.0` and the repository is
-  `cbusillo/odoo-shared-addons`. Renovate reads the consumer's base branch
+  It also moves an already exact `[repos.shared_addons].ref` pin for
+  `cbusillo/odoo-shared-addons` to its `main` head commit when
+  `[build].odoo_version` is `20.0`. Renovate reads the consumer's base branch
   manifest, so landing its Odoo 20 conversion activates these updates; an
   unmerged conversion does not. Odoo 19 shared-addons pins stay unchanged.
   Shared-addons updates use ordinary visible pull requests, preview checks