Skip to content

[18.0] [MIG] ai_automation -> ai_server_action#81

Open
angelmoya wants to merge 9 commits into
OCA:18.0from
angelmoya:18.0-mig-ai_automation
Open

[18.0] [MIG] ai_automation -> ai_server_action#81
angelmoya wants to merge 9 commits into
OCA:18.0from
angelmoya:18.0-mig-ai_automation

Conversation

@angelmoya

@angelmoya angelmoya commented Jun 23, 2026

Copy link
Copy Markdown
Member

[MIG] ai_automation -> ai_server_action: migration to 18.0

  • Renamed module from ai_automation to ai_server_action
  • Removed ai_connection model (now in base ai_connection module)
  • Added output modes: post_message, update_record, store_variable, none
  • Added markdown rendering support for HTML fields
  • Added template variable support via Qweb
  • Rewrote tests using FakeModelLoader pattern (no real API calls)

Depends on #77

@angelmoya angelmoya mentioned this pull request Jun 23, 2026
- Renamed module from ai_automation to ai_server_action
- Removed ai_connection model (now in base ai_connection module)
- Added output modes: post_message, update_record, store_variable, none
- Added markdown rendering support for HTML fields
- Added template variable support via Qweb
- Rewrote tests using FakeModelLoader pattern (no real API calls)
@angelmoya angelmoya force-pushed the 18.0-mig-ai_automation branch from 6cfe6d3 to 622b6a2 Compare June 23, 2026 10:04
@pedrobaeza

Copy link
Copy Markdown
Member

Please keep the previous name for consistency across versions, and allowing to be broader.

@angelmoya

Copy link
Copy Markdown
Member Author

Please keep the previous name for consistency across versions, and allowing to be broader.

Thanks for the heads-up. This name change is already reflected in the current roadmap #73 .

In any case, we are still reviewing the approach to see if a migration script is necessary or how exactly we should handle it, whether through a direct change or by creating a migration script.

@angelmoya

Copy link
Copy Markdown
Member Author

Additionally, regarding the commit order, it might be better to split it. We could first do the migration and adaptation work to version 18 relying on the connection, and then handle the name change in a separate, subsequent commit.

This way, the actual changes between versions would be much easier to track and review.

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.

6 participants