Skip to content

[19.0][MIG] queue_job_subscribe: Migration to 19.0 - #1

Open
alan196 wants to merge 1 commit into
19.0from
19.0-mig-queue_job_subscribe
Open

[19.0][MIG] queue_job_subscribe: Migration to 19.0#1
alan196 wants to merge 1 commit into
19.0from
19.0-mig-queue_job_subscribe

Conversation

@alan196

@alan196 alan196 commented Jul 30, 2026

Copy link
Copy Markdown

Migration of queue_job_subscribe to 19.0 (Starka 17.0 -> 19.0 project).

The 19.0 branch already contained the module as an 18.0.1.0.0 copy with installable: False (branch-creation bot). This PR adapts it in place, taking the module changes from the open OCA migration PR OCA#845 by @tishmen (module content only, without its temporary CI/test-requirements commits).

Changes:

  • Bump version to 19.0.1.0.0, set installable: True
  • Tests: groups_id -> group_ids (res.users field renamed)
  • Regenerate README.rst / static description for 19.0
  • Remove the module from the pre-commit excluded addons list

Validation:

  • pre-commit (repo OCA config): all hooks Passed
  • Install + tests on scratch DB (Odoo 19, queue_job 19.0.2.0.3): 0 failed, 0 error(s) (4 tests)

🤖 Generated with Claude Code

- Bump version to 19.0.1.0.0 and set installable to True
- Rename groups_id to group_ids in tests (res.users field renamed in 18.0+)
- Regenerate README.rst and static/description/index.html for 19.0 branch
- Remove module from pre-commit excluded (not installable) addons list

Changes taken from OCA migration PR OCA#845 by @tishmen
(module content only, without the temporary CI commits).

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.

2 participants