Skip to content

[19.0][MIG] queue_job_cron_jobrunner: Migration to 19.0 - #2

Open
alan196 wants to merge 2 commits into
19.0from
19.0-mig-queue_job_cron_jobrunner
Open

[19.0][MIG] queue_job_cron_jobrunner: Migration to 19.0#2
alan196 wants to merge 2 commits into
19.0from
19.0-mig-queue_job_cron_jobrunner

Conversation

@alan196

@alan196 alan196 commented Jul 30, 2026

Copy link
Copy Markdown

Migration of queue_job_cron_jobrunner to 19.0 for the Starka 17->19 project.

Source

Changes

  • __manifest__.py: version 19.0.1.0.0, installable: True.
  • README/index.html: 18.0 -> 19.0 links (Weblate, Runboat, GitHub tree, issue template).
  • .pre-commit-config.yaml: remove module from the NOT INSTALLABLE exclude list.
  • Extra commit: pylint invalid-name disables for upstream at argument / assertTriggerAt helper and README trailing-whitespace cleanup so pre-commit-vauxoo Mandatory+Optional pass (kept code identical to OCA otherwise).

No 19.0 API breakage found: tools.ustr, odoo.service.model.PG_CONCURRENCY_ERRORS_TO_RETRY, queue_job.controllers.main.PG_RETRY, ir.cron fields (priority, interval_*) all verified against the 19.0 codebase. No tree/attrs/states/category_id/_() occurrences.

Tests

  • pre-commit-vauxoo -p queue_job_cron_jobrunner: Mandatory Passed, Optional Passed.
  • Fresh DB install with -i queue_job_cron_jobrunner --test-enable: 0 failed, 0 error(s) (7 tests, queue_job 19.0.2.0.3 from this repo).

Upstream to watch: once OCA#876 merges, this can be synced/rebased against OCA 19.0.

🤖 Generated with Claude Code

tishmen and others added 2 commits July 30, 2026 18:12
Split from OCA#843 as requested; this commit only migrates queue_job_cron_jobrunner.

(cherry picked from commit 774b572)
- Add pylint invalid-name disables for upstream 'at' argument and
  assertTriggerAt helper (kept to minimize diff with OCA).
- Remove trailing whitespace in README.rst (doc8).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@jarsabot

Copy link
Copy Markdown
    **WARNING**: Could not link to Odoo task. Record ID not found in the title of the MR, supported formats:
{ record type }#{ number }

Available types: 'task#', 't#' (case insensitive)

Examples:

  • task#123

  • i#123

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants