Tags

Tags give the ability to mark specific points in history as being important
  • 1.0.0-rc1

    no Media Bias/Fact Check ratings in the release (MBFC's data is not GPL); drush factcheck:sync-bias-ratings now needs --file or --fetch. Security audit fixes before the coverage review: fact check results need administer factcheck settings to edit or delete, standalone fact check and terms analyzer are restrict access, and PageFetcher pins each hop to the checked public address (requires curl), refuses non-global ranges including 100.64.0.0/10 and reads at most 5 MB. New experimental terms submodule (terms of service / privacy policy analysis, Spanish-measured only). Requires AI ^1.5. Run drush updb.
  • 1.0.0-beta4

    Decision models: a typesafe backend for TypeSafe Jev and self-hosted Laya (System One), an openai_decisions backend for OpenAI's gpt-6-luna, and AI core's Decision operation (AI 1.6+) through the experimental ai_provider_universal_decision submodule. Smart routes fail over around servers that are down, including between local and hosted decision models. Also: models filtered by the capabilities AI core asks for, DeepSeek's current peak schedule (from SeekPeak), a server form fix for self-hosted servers on hosted backends, and an SSRF fix for redirects
    in the standalone fact check. No update hooks; DeepSeek servers should run drush aipdm. Jev and Luna are not yet verified against their live APIs.
  • 1.0.0-beta3

    Adds native (non-OpenAI) inference with Anthropic and DeepSeek backends, per-model extra request parameters, and fixes a server form that could not be saved when a provider reports a negative price (OpenRouter openrouter/auto). Run drush updb — update 10103.
  • 1.0.0-beta2

    Content governance (EU AI Act Art. 50)
    No more drupal/ai patches: model IDs now use a dot separator (`server.model`, routes `route.<id>`) and model selects are flat `model_id => label` maps
    new recipes
  • 1.0.0-beta1

    First beta of the 1.0 line. Feature-complete for wider testing:
    ten backends, smart routing, fact check, extensibility events and
    admin-tunable prompts.
    
    Since 1.0.0-alpha1:
    
    - New backends: ollama (local, native /api/show enrichment: context,
      capabilities, free-cost prefill) and groq (live pricing, context and
      supported_features from the catalog).
    - Models: catalog features persisted from discovery; per-model sampling
      overrides (temperature, top_p, penalties) with vendor-recommended
      defaults; quality-tier prefill via family/size heuristics plus a
      price-band fallback for live catalogs.
    - Smart Router: required catalog features on routes, verifier model,
      optional complexity-classifier model, new Smart routing settings form,
      decision log as editable Views; savings report moved to
      /admin/reports/ai-router-savings.
    - Fact check: admin notifications (event + optional mail), per-role scan
      flood limits, MBFC bias import, results entity + Views history,
      expanded trusted-site seeds (PubMed, Nature, Science, arXiv, Reuters, AP).
    - All eight tunable LLM prompts editable from the admin UI with sprintf
      token validation (empty = shipped default).
    - Extensibility: ModelPostCallEvent and ModelsDiscoveredEvent join the
      pre-call gate; routed calls tagged for ai_observability attribution.
    - Hardening: SSRF guard on standalone URL scans, prompt-injection
      mitigations in shipped templates, silent failures now logged.
    - Requires Drupal 11.1+ / 12, PHP 8.3+. No update hooks needed from
      alpha1; re-export site config after upgrading.
  • 1.0.0-alpha1

    ⚠️ Breaking change: not compatible with 1.0.x-dev installs.**
    
    Entity types and plugin IDs were renamed in this release. Sites running a `1.0.x-dev` checkout cannot update in place — you will need to uninstall the dev version and install this release fresh (export any trusted-site curation or route config you want to keep first).
    
    We took this one-time break deliberately, before the first tagged release, to give entities and plugins proper, unambiguous names instead of squatting generic ones (Just added ai_ in entities and Ai in plugins) — better now than after sites depend on them. Apologies for the inconvenience; this was the least painful moment to do it, sorry for the trouble.