Skip to content

All versions since 0.3.0

0.3.0

As it stood at this release: the repository · the docs · the knowledge bundle · the release

Added

  • The website’s home page offers an Install button, which opens the install page, beside the four default buttons.
  • linkml-author names the adapt route beside a KTL bundle. A schema published on its own stays as it is, and the copy lokf adapt writes is the domain schema; the preflight’s lokf line says when the justfile names such a copy.

0.3.1

As it stood at this release: the repository · the docs · the knowledge bundle · the release

Security

  • The sidecar copies and the skills pin are at Knowledge Trust Ladder v0.55.2. The release changed .lokf/scripts/knowledge-preflight.sh and .lokf/scripts/knowledge-sync.sh here.

0.3.2

As it stood at this release: the repository · the docs · the knowledge bundle · the release

Changed

  • The project’s persistent identifier is https://w3id.org/ktl/linkml-sidecar/. The README, the plugin’s homepage and the website’s README link through it. No skill change.

Fixed

  • The assumptions catalogue concept links linkml-project-copier#187 from its body, not its references. A typed relation names a concept, so the KTL federation gate failed on that outside URL.

Security

  • The sidecar copies and the skills pin are at Knowledge Trust Ladder v0.56.1. The release changed .github/workflows/knowledge-registrar.yaml, .github/workflows/knowledge-librarian.yaml, .github/workflows/knowledge-release.yaml, .lokf/scripts/knowledge-preflight.sh, .lokf/scripts/knowledge-sync.sh, website/astro.config.mjs, website/scripts/check-links.mjs, website/scripts/config.mjs, website/scripts/markdown-ktl.mjs, website/scripts/raw-html.mjs, website/scripts/routes.mjs, website/scripts/sync.mjs, website/src/components/ConceptCard.astro, website/src/components/ConceptPreviews.astro, website/src/components/KnowledgeGraph.astro, website/src/components/Mermaid.astro, website/src/components/Neighbourhood.astro, website/src/components/TrustChart.astro, website/src/content.config.ts, website/src/pages/og/[...route].ts, website/src/styles/catalogue.css and .github/workflows/knowledge-website.yaml here.

0.3.3

As it stood at this release: the repository · the docs · the knowledge bundle · the release

Security

  • The sidecar copies and the skills pin are at Knowledge Trust Ladder v0.56.2. The release changed .lokf/.gitignore here.

0.3.4

As it stood at this release: the repository · the docs · the knowledge bundle · the release

Added

  • linkml-author’s generator pitfalls cover seven more behaviours seen on linkml 1.12.1. gen-owl types a property from its range, so a union slot needs a range and an annotation property implements; it writes no deprecated, and keeps a label in aliases as skos:altLabel. The SQL generator writes a table for each multivalued slot of each class, and gen-project ignores a generator name it does not know, such as the template’s markdown and sqlddl. gen-owl’s type_objects defaults differ between gen-project and the command line, and the gen-project row now says that it runs gen-java since 1.12.

Changed

  • The .lokf toolkit floor is lokf 0.9.0. Knowledge Trust Ladder v0.60.0’s lokf-check-refs passes --check-excerpts, which lokf 0.8.0 lacks.

Security

  • The sidecar copies and the skills pin are at Knowledge Trust Ladder v0.59.0. The release changed .github/workflows/knowledge-registrar.yaml, .github/workflows/knowledge-librarian.yaml, .github/workflows/knowledge-release.yaml, .github/workflows/knowledge-sync.yaml, .lokf/scripts/knowledge-conventions.sh, .lokf/scripts/knowledge-conventions.py, .lokf/scripts/knowledge-preflight.sh, .lokf/scripts/knowledge-apply.sh, .lokf/scripts/knowledge-apply.py, .lokf/scripts/knowledge-report.sh, .lokf/m365/ktl-docent-m365.md, website/package-lock.json, website/package.json, website/scripts/config.mjs and .github/workflows/knowledge-website.yaml here.

0.4.0 Latest

Added

  • In KTL mode the scaffold writes the schema’s path as [tool.lokf] schema in .lokf/pyproject.toml too. A lokf command given no --schema then reads the schema the recipes check against, and the preflight reports the table and warns when it names another path.