Skip to content

omp-spec-kit v2.6.0

Choose a tag to compare

@github-actions github-actions released this 21 Sep 13:33
· 24 commits to main since this release

Superseded by v2.6.1 — the app ZIP in this release is internally consistent (CI-built, digest-verified) but its build was not byte-reproducible across timezones; v2.6.1 fixes that. Use v2.6.1.

omp-spec-kit v2.6.0

Included changes

  • Moves canonical specifications out of product repositories into a dedicated service-owned specs repository; all specification reads and writes go through the spec-registryd MCP service with YouTrack-backed verified identity, roles, and project scopes.
  • Publishes an immutable annotated git tag spec/<project>/<slug>/<version> plus an insert-only ledger row when an authored Status: becomes ACTIVE; identical content no-ops, different content under an existing version is rejected and surfaced in GET /drift.
  • Adds versioned reads: spec_documents(action:"read", version) serves bytes from the tagged commit with digest re-verification and path containment.
  • Adds the onboarding API (per-user YouTrack token mint + ready .mcp.json snippet), managed remote plugin mode, and the YouTrack app packaged in CI via the official youtrack-app CLI.
  • Retires the in-repository .specs corpus: local trees are historical artifacts only — consumers and agents must go through the service.

Verified release

  • Candidate digest: 8984b4e2234481edf24a5f742063194c1db0d016750cc767cc80ec98c986fc17
  • Package tree digest: 91ecb042bde0bba4fc4ac7de3cc1bbe4362932e53f30c16f4d5fab34ea617f2a
  • Archive SHA-256: 2f79e85046478e4520304b42534e0f90e094152a2b91e85f12149375c4c5526e
  • YouTrack app: spec-graph-app-1.0.25.zip (SHA-256 efeead2bbdfcf1dc50573f498ffce2b611f19828a84e0f588e0c7eb485e157df) — upload via Administration → Apps → Add app… → Upload ZIP file
  • Peeled tag commit: 20fe46158fd50ba31cd47428657c7cb21f73a9db
  • OMP runtime: 18.0.11
  • Distribution evidence: lifecycle producers, Docker BDD, manager discovery, and nine closed MRI receipts.

Install or upgrade at project scope, reload plugin metadata, then start a fresh OMP session before invoking MCP tools.