Skip to content

docs: add version compatibility table to SPEC.md (PILOT-421)#3

Closed
matthew-pilot wants to merge 1 commit into
mainfrom
openclaw/pilot-421-20260618-112940
Closed

docs: add version compatibility table to SPEC.md (PILOT-421)#3
matthew-pilot wants to merge 1 commit into
mainfrom
openclaw/pilot-421-20260618-112940

Conversation

@matthew-pilot

Copy link
Copy Markdown
Collaborator

What

SPEC.md v0.5 does not include a version compatibility table mapping spec versions to Pilot Protocol software releases. This adds one near the top of the spec (after the title block).

Why

Developers and operators need a quick reference to know which spec version corresponds to their software release. The spec says v0.5 but code is at v1.11.x — the table clarifies the mapping.

Verification

  • Rendered markdown readable
  • Table format clean
  • No code changes needed (pure docs repo)

Closes PILOT-421

Add a version compatibility table near the top of SPEC.md mapping
spec versions (v0.1–v0.4 → code v1.0–v1.3.x, v0.5 → v1.4–v1.11.x)
so developers can quickly determine which spec version corresponds
to their software release.

Closes PILOT-421
@matthew-pilot

Copy link
Copy Markdown
Collaborator Author

Superseded by PR #5 (re-created with updated content)

@matthew-pilot matthew-pilot deleted the openclaw/pilot-421-20260618-112940 branch June 23, 2026 12:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant