Repository navigation
Update shared-addons pins for Odoo 20 consumers - #408
Conversation
|
Review result: weighed Anthropic claude-opus-5-5 reviewed the source at 8dd0217. Weighed for current head 8031284, which changes only the requested docs clarification. Acted on: clarified that shared-addons updates require an already exact pin. Actual extraction controls: CM main=one shared dependency; OPW/website main=none; all retain two devkit/runtime deps. Baseline preset fails eligible-CM extraction. Exact-pin, missing-build, commented-build and table-order controls pass. Strict Renovate repo config validation, 22 workspace tests, whole-repo Ruff lint/format and diff checks pass. Native inspection is explicitly UNKNOWN for unsupported JSON/Markdown selection under the recorded standing Director exception linked in the PR. Required consumer checks and current-head CI remain pending. |
|
Required tenant consumer-build checks passed for current head 8031284.
Both retained consumer-build-check-1 artifacts were downloaded and inspected: runtime_commit equals the PR head, source_commit equals the respective normal main snapshot, platforms and dependency_provenance.target_platforms are linux/amd64, and runtime/tenant lock provenance names those exact commits. These are build-only checks; nothing was published or deployed. Current-head CI is green: five checks passed, zero failed/pending, complete terminal workflow evidence. Weighed review and the exact native inspection UNKNOWN reason/standing exception are recorded above. All source readiness gates are met under that exception. No tenant pin, runtime, data, production or Client acceptance change follows. |
|
Ready for the merge train Head: 8031284 |
|
Ready for the merge train Head: 8031284 |
|
Launchplane completed the merge-train step for this pull request.
Launchplane finished the merge-train step for this pull request. Launchplane manages this comment and will update it as the train moves. |
…746922aeeb7db4b: merge PR #408
Eligible Odoo 20 consumers now get shared-addons pin updates through the existing Renovate preset. The manager parses the base-branch TOML and selects only an exact
repos.shared_addons.reffor the shared repository whenbuild.odoo_versionis20.0. Odoo 19 pins stay unchanged; existing devkit/runtime and workflow managers are preserved.Closes #131.
Validation: Renovate 44.181.5 strict repository-config validator and actual extraction/replacement controls pass. Fresh CM main extracts one shared dependency; OPW and website main extract none; all retain both devkit/runtime dependencies. Replacing a digest changes only the shared-addons ref. Reordered tables work; non-exact refs, missing build metadata and commented Odoo20 declarations are ignored. The eligible-CM assertion fails on the original preset. 22 workspace tests, whole-repo Ruff lint/format and diff checks pass. Full unit suite runs in CI. Consumer-build results will be recorded before Ready.
Native inspection: UNKNOWN/isolated_backend_unavailable, run b658571a-a6cb-4cff-860b-ae2ea7282859. The configured PyCharm lane cannot inspect JSON; no native worker covers Markdown. No clean verdict is claimed. Proceeding with the explicit reason under the standing temporary Director exception, retained by the October 26 decision; the current decision/unfinished inspection work was rechecked.
Source-only delivery: no consumer pin, runtime/configuration, production, Client acceptance, data, identity or access change. No Renovate force run. Production continues through the normal Client-accepted release.
Removed: manual shared-addons repinning for eligible Odoo20 consumers. Net lines: +24; the existing Renovate preset needs one parsed-manifest manager, its update rule and docs to cover the missing dependency. No second updater or site registry.
Client test notes
Nothing for the Client to test: this changes shared pin-update automation only. It moves no tenant pin and changes no running product; any later update PR is reviewed through its normal preview and release path.