Skip to content

[20.0][MIG] hr_holidays_google_calendar: Migration to 20.0 - #74

Closed
mav-adhoc wants to merge 3 commits into
ingadhoc:20.0from
adhoc-dev:20.0-t-76665-mav
Closed

mav-adhoc wants to merge 3 commits into
ingadhoc:20.0from
adhoc-dev:20.0-t-76665-mav

Conversation

@mav-adhoc

Copy link
Copy Markdown
Contributor
  • google.calendar.sync is split into google.sync and google.event.sync: _google_insert now takes the target calendar, so the override follows the new signature.
  • TIMEOUT is no longer exported by google_calendar.models.google_sync; it comes from google_account.models.google_service, which is where 19.0 took it from as well (same value).
  • i18n regenerated; module name and summary translated.
  • depends and auto_install unchanged. No data migration script is needed: the module declares no fields, models or data.

Checks: migrator and upgrade_code (no changes), static checks, imports, permissions, pre-commit. Installed and updated on a clean 20.0 database; the module ships no tests.

Heads-up for review, not introduced here: in odoo/odoo 20.0 GoogleEventSync.write calls _google_insert without the new calendar argument (google_calendar/models/google_event_sync.py:68), so that path raises a TypeError upstream. The create path used by hr_holidays passes all three arguments.

Tarea: https://www.adhoc.inc/odoo/project.task/76665

weblate and others added 2 commits October 23, 2026 15:03
- google.calendar.sync is split into google.sync and google.event.sync:
  _google_insert takes the target calendar as a new argument, so the
  override follows the 20.0 signature.
- TIMEOUT is no longer exported by google_calendar.models.google_sync:
  import it from google_account.models.google_service.
- Regenerate i18n and translate the module name and summary.
@roboadhoc

Copy link
Copy Markdown
Contributor

Pull request status dashboard

@mav-adhoc mav-adhoc changed the title [WIP] [20.0][MIG] hr_holidays_google_calendar: Migration to 20.0 [20.0][MIG] hr_holidays_google_calendar: Migration to 20.0 Oct 23, 2026
…apes

Odoo 20 calls _google_insert with two signatures: google_event_sync.py:68
still omits `calendar`, while lines 129 and 174 pass it. Upstream wraps the
method in @after_commit, which takes any arguments and defers the call, so
without this module the mismatch only ends as a post-commit warning. The
override ran first and raised TypeError inside the transaction, so
confirming a draft event failed. It now forwards whatever it gets.

Also add the first test of the module: it covers both call shapes and the
send_updates=False suppression, and fails with the previous signature.

Change note: en Odoo 20, confirmar un evento de calendario en borrador
fallaba con error en las bases que tienen instalado este modulo (se instala
solo). Ahora confirma bien, y se mantiene que una ausencia aprobada no le
mande la invitacion de Google a los asistentes.
@les-adhoc

Copy link
Copy Markdown
Contributor

@roboadhoc r+ nobump rebase-ff

@roboadhoc

Copy link
Copy Markdown
Contributor

Merge method set to rebase and fast-forward.

roboadhoc pushed a commit that referenced this pull request Oct 30, 2026
(cherry picked from commit 1dd74a8)

Part-of: #74
Signed-off-by: Luciano Esperlazza <[email protected]>
roboadhoc pushed a commit that referenced this pull request Oct 30, 2026
- google.calendar.sync is split into google.sync and google.event.sync:
  _google_insert takes the target calendar as a new argument, so the
  override follows the 20.0 signature.
- TIMEOUT is no longer exported by google_calendar.models.google_sync:
  import it from google_account.models.google_service.
- Regenerate i18n and translate the module name and summary.

Part-of: #74
Signed-off-by: Luciano Esperlazza <[email protected]>
@roboadhoc roboadhoc closed this in 34d3256 Oct 30, 2026
@roboadhoc
roboadhoc deleted the 20.0-t-76665-mav branch October 30, 2026 15:06
@roboadhoc roboadhoc added the 19.1 label Oct 30, 2026

This branch was previously deployed

1 inactive deployment
merge — daa0c55f Deployed Oct 30, 2026 by roboadhoc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants