Part of ITB 0.1.2 release - See master release

🏗️ Infrastructure​

Open documentation with licence badges, and the use case as a dimension​

The documentation site no longer withholds material by licence level — it publishes it and marks it. Every changelog entry carries a badge saying which licence the change needs (Standard or Enterprise), and the release overview groups its counts by licence so the split is visible before you read a single entry.

A pack declares how it is delivered​

A capability pack now states in its own configuration whether it is delivered encrypted or in the open. The field is distribution, it takes exactly two values — encrypted and open — and it is mandatory for a capability pack: there is no default value, and a pack without the field stops the scripts that read it rather than being guessed at in either direction.

One marketplace item installs several components​

The marketplace has a sixth group, Bundles. A bundle is one item that installs several components at once — a model with its type configuration, template packs, capability packs and quality rule groups — in the order that makes them work.

🐞 Fixes​

Git remotes that are not HTTPS URLs work again​

Push and pull accept the remote address in the form your Git host gives you. An SSH address — git@github.com:your-org/your-repo.git, the one behind GitHub's Clone with SSH button — is now handed to Git unchanged.

Das Benutzerhandbuch wird im öffentlichen Image wieder angezeigt​

Wer ITB nach der Anleitung aus dem öffentlichen Repository startet und im Hilfe-Menü auf Documentation klickt, bekam eine leere Seite mit der Meldung „Your Docusaurus site did not load properly." Die Seite selbst kam an — nur keine ihrer Dateien.

Part of ITB 0.1.1 release - See master release

🏗️ Infrastructure​

API-deliverable capability i18n​

Capability labels (button/menu titles, form field labels, placeholders, wizard steps, toast messages) used to live in the client's monolithic messages.ts dictionary, mixed in with app-shell strings. They are now split out so a capability owns its strings as data: every descriptor references its own overlap-free capabilities.<id>.* namespace, and those strings live in per-locale JSON under registry/i18n/{public,enterprise}/{en,de}.json.

Part of ITB 0.1.0 release - See master release and WebApp Details

✨ New Features​

Git Push/Pull for Model Exchange​

Connect to a Git repository and push or pull models directly from the API. This replaces the previous file-based export/import workflow with a proper version-controlled exchange mechanism.

Git Origin Tracking with Optimistic Locking​

The API now tracks the Git origin of each model and uses optimistic locking to prevent accidental overwrites when multiple users collaborate on the same model.

Template Artifact Export as Zip​

Generated template artifacts can now be downloaded as a single zip file, making it easier to distribute and deploy generated code.

Generate-All Cleans Stale Output​

The generate-all endpoint now removes stale output files before re-generating, ensuring the output directory always reflects the current model state.

🔧 Improvements​

URL Pattern/Scheme Cleanup​

API endpoint URLs have been reorganized for consistency. All endpoints now follow a uniform naming convention under /api/v1/.

⚠️ Breaking Changes​

Removed Legacy PocketBase and Data Vault Routers​

The legacy PocketBase proxy endpoints and the standalone Data Vault router have been removed. Clients previously depending on these must migrate to the standard model and Git-based endpoints.

Summary​

ITB API 0.1.0 shifts model exchange from file-based workflows to Git-native operations, adds collaborative safeguards via optimistic locking, and cleans up the API surface by removing deprecated routers.

Part of ITB 0.0.7 release - See master release and WebApp Details

✨ New Features​

Metadata Export File​

Model exports now automatically include a _metadata.json file that captures comprehensive version information and statistics about the exported model.

What's included:

• Version information: ITB frontend, API, and library versions
• Export timestamp: When the model was exported
• Statistics: Entity, relation, viewpoint, and node counts

New API Endpoint: /pb_info​

A new endpoint has been added to retrieve version information from PocketBase (ITB Frontend):

• Method: GET
• Path: /pb_info
• Returns: JSON with current version information

This endpoint calls the PocketBase /getVersion hook to retrieve the current version of the ITB frontend.

Example Metadata File​

{
  "itb_version": "0.0.7",
  "api_version": "0.0.7",
  "banian_library_version": "0.5.2",
  "last_updated": "2026-02-12 14:30:45",
  "entity_count": 42,
  "relation_count": 156,
  "viewpoint_count": 8,
  "node_count": 234
}

Benefits​

• Version tracking: Know exactly which tool versions created each export
• Debugging: Quickly identify version mismatches when troubleshooting issues
• Auditing: Track when models were last updated
• Statistics: Get a quick overview of model complexity
• Automation: Parse metadata programmatically for CI/CD pipelines

Summary​

This release enhances data model traceability by automatically capturing version information and statistics in every export. The new metadata file makes it easy to understand the context of any model export and supports better debugging and automation workflows.