# odoosky-odoo

Pinned Odoo platform images for OdooSky v3.

## Why this repo exists

Customer instances must pull from a Git-pinned, OdooSky-controlled
image. The 2026-05-04 incident proved that pulling Docker Hub's
rolling `odoo:18.0` tag = inheriting whatever Odoo SA's nightly cron
shipped that morning. Their May 4 build ships a SQL regression that
breaks every login on every new pod.

This repo is the **source of truth** for which Odoo nightly each
major is pinned to. The chart `instance-template-v3` reads from
this list. ArgoCD reconciles. Customer instances always pull a build
we tested.

## Where the images live

```
registry.odoosky.cloud/odoosky/docker-mirror/odoo:<pinnedTag>
```

Same registry path that already mirrors upstream images for BuildKit
during addon builds. We're now also using it for runtime Odoo.

## How to bump

See `versions.yaml` — the bump policy + smoke checklist live there.
The shape: smoke first, push to mirror, update versions.yaml, commit.

## What this is NOT

- A build-from-source pipeline. Today we mirror upstream nightlies as
  exact bytes. Future enhancement: build from source at a pinned commit
  with our own patches.
- An automated bump. P5 in the rollout plan adds a Gitea Actions job
  that auto-builds + auto-smokes new candidates and proposes bumps.
  Until then, bumps are operator-clicked on lab1.