[v2.0.1] - 2025-30-06

Added

• Added support for more languages in the search widget: Arabic, Catalan, Danish, Dutch, English, Finnish, French, German, Greek, Hindi, Hungarian, Indonesian, Italian, Lithuanian, Nepali, Norwegian, Portuguese, Romanian, Russian, Croatian, Slovenian, Spanish, Swedish, Tamil, Turkish
  • For any other language a default parser will be used.
• UI language selection expanded in the configuration drawer.
• Web search language selection added to the Search Widget configuration.

Changed

• Language configuration is now split into two distinct settings: UI Language and Web Search Language.
  • These can now be managed independently.
  • Existing integrations using the previous unified language setting remain supported for backward compatibility.

[v2.0.0] - 2025-16-06

Added

• Web Search feature
  • Dashboard - Added Search component generation and playground.
• Tenants can now use LLM configuration sets, LLM API keys, and prompt templates that are used by default.
• Repository types: Folder, Semantic, Web Search
  • Existing repositories are automatically converted to Semantic repositories
• S3: All file/folder paths are now also kept in the database
  • An initial sync between S3 and database is required for each tenant and each S3 bucket
• S3: Repository locking mechanism (making repository and all its files read-only)
  • Folders are always unlocked
    • They cannot be marked as Semantic during Knowledge base update on their respective bucket
  • All Semantic repositories are locked during Knowledge base update on their respective bucket
  • Web Search repositories are always locked
    • They can only be renamed and deleted if and only if not being currently crawled
    • They cannot be unmarked
• S3: Minor restrictions for moving/deleting files and folders
• Keeping track of last preprocessing date for each Semantic repository
• Added endpoint that generates contents for a GitHub action file (automatic preprocessing on push)
• Auto-recrawl feature
  • Each repository has a separate re-crawl frequency (in hours)
  • Every full hour, Dokko checks if any re-crawls need to be started
  • If multiple automatic re-crawls need to be started, the repository with the oldest "previous crawl date" has priority
  • Crawl parameters are copied from the previous crawl on that repository
  • Possible to disable auto-recrawl on any repository
    • To re-enable it, it is required to manually start a crawl on the repository