Skip to content

v0.10.0

Latest
Latest

Choose a tag to compare

View all tags
@zircote zircote released this 08 Oct 22:52
· 1 commit to main since this release
v0.10.0
This tag was signed with the committer’s verified signature.
zircote Robert Allen
GPG key ID: B86AD330E26E59D4
Verified
Learn about vigilant mode.
23ccaf5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

[0.10.0] - 2026-10-08

Aligns mif-docs with MIF specification 1.4.2 (the coordinated release of
the 1.4.x line; its schemas are byte-identical to 1.4.1's).

Changed

  • MIF pin: MIF_SPEC_VERSION and schema/VENDOR.lock move from 1.4.1 to
    1.4.2, the coordinated MIF release published with artifacts.
  • Schema pin: hydrate-schema fetches the pinned MIF release's mirror
    (MIF_SPEC_VERSION, 1.4.2, in scripts/hydrate-schema.mjs) instead of the
    floating latest, so a new MIF release no longer changes what CI validates
    against. node scripts/hydrate-schema.mjs latest still fetches the newest
    release, and index.json is fetched only then.
  • Ids (breaking for content): MIF 1.4.0 requires a concept @id of
    urn:mif:<uuid>. Every template and doc id, and every urn:mif:
    reference to one (relationship targets, provenance wasDerivedFrom), moves
    from its slug to uuid5(uuid5(NAMESPACE_URL, "https://mif-spec.dev"), slug),
    the derivation MIF's migration script and mif-rs use; so do the id:
    examples in the tutorials, how-to and evals, and the x-related-adr /
    x-c4-companion cross-references. Reserved urn:mif:activity: and other
    non-concept provenance ids are unchanged.
  • mif-frontmatter: id MUST be a UUID; the skill says how to mint or
    derive one.
  • mif-validate: says a per-document pass meets the L1 document floor, and
    that MIF 1.4.0+ Level 1 also requires an OKF bundle.
  • schema/profiles/level-1.json: description matches 1.4.0's L1 core
    (UUID @id; conceptType or the deprecated memoryType).

Security

  • Deps: osv-scanner.toml (root and site/) records the four advisories
    left after the Dependabot updates, none with a fix in range: katex, braces,
    smol-toml, and postcss-selector-parser, each build-time or dev-only.
  • Deps: npm overrides now force the patched releases, replacing three of
    those waivers: katex ^0.18.2 (GHSA-238p-pmpm-9mq7, root and site/),
    smol-toml ^1.9.0 (GHSA-r4xh-jqrq-34v2, root), and postcss-selector-parser
    ^7.1.6 (GHSA-rj75-hqrm-r3gf, site/). Only the braces waiver
    (GHSA-vfj7-8cjw-p6xm, no fixed release) remains in either config.

Fixed

  • hydrate-schema: latest resolves through index.json's
    aliases.latest (the field the catalog publishes), not a nonexistent
    top-level latest.
  • mif-validate/mif-convert/mif-to-pdf: accept a document typed only
    by the deprecated memoryType, which MIF 1.4.0's schema allows; the
    projection passes memoryType through and synthesizes no conceptType.
Assets 3
Loading