You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Docs update: Ultimate AI Connector for Compatible Endpoints v2.2.0 #186
Ultimate AI Connector for Compatible Endpoints v2.2.0 — released 2026-09-09
Required doc updates
docs/addons/ultimate-ai-connector-compatible-endpoints/index.mdx — document compatible endpoint image generation and model discovery/prefetch configuration and usage.
docs/developer/integration-guide/ — document image-generation capability support and compatibility considerations for older WordPress AI Client SDK versions.
docs/developer/rest-api/ — document any endpoint/API expectations for image generation and model discovery where applicable.
Changelog entry
= 2.2.0 =
Version 2.2.0 - Released on 2026-09-09
- New: Compatible endpoints can now generate images through the WordPress AI Client when the endpoint supports image generation.
- New: Model discovery now prefetches and presents available endpoint models more reliably in the connector settings.
- Fix: Cloud model selection and structured output requests now work correctly with compatible endpoints.
- Fix: Image support is guarded for older AI Client SDK versions so the plugin remains compatible while newer SDKs are unavailable.
This issue was created via a bare gh issue create call that bypassed the gh_create_issue wrapper in shared-constants.sh. The framework's reconcile pass (reconcile_labelless_aidevops_issues in pulse-issue-reconcile.sh, t2112) has backfilled origin:worker + tier:standard as conservative defaults and extracted hashtag labels from the body.
Why this matters: issues missing origin/tier labels are invisible to the dispatch-dedup guard and the label-reconciler. Without this backfill, the pulse would have left this issue unblessed forever.
Next time: use gh_create_issue (defined in shared-constants.sh, sourced via the framework PATH) instead of bare gh issue create. The wrapper applies origin + auto-assign + sub-issue linking automatically. See AGENTS.md → "Origin labelling (MANDATORY)".
This comment is idempotent; the HTML sentinel prevents duplicates on subsequent pulse cycles.
Activity
superdav42 commentedon Sep 10, 2026
This issue was created via a bare
gh issue createcall that bypassed thegh_create_issuewrapper inshared-constants.sh. The framework's reconcile pass (reconcile_labelless_aidevops_issuesinpulse-issue-reconcile.sh, t2112) has backfilledorigin:worker+tier:standardas conservative defaults and extracted hashtag labels from the body.Why this matters: issues missing origin/tier labels are invisible to the dispatch-dedup guard and the label-reconciler. Without this backfill, the pulse would have left this issue unblessed forever.
Next time: use
gh_create_issue(defined inshared-constants.sh, sourced via the framework PATH) instead of baregh issue create. The wrapper applies origin + auto-assign + sub-issue linking automatically. SeeAGENTS.md→ "Origin labelling (MANDATORY)".This comment is idempotent; the HTML sentinel prevents duplicates on subsequent pulse cycles.
aidevops.sh v3.32.317 automated scan.