docs: state the specification version as 1.7 - #47
Open
delchev wants to merge 1 commit into
Open
Conversation
The spec overview and the nav version badge said "Version 1" / "v1" with no minor; intent-specification#63 cuts versions/1.7.md, so the site now names that version and links the normative file. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the version the site shows — the spec overview heading line (
Version 1→Version 1.7, now linkingversions/1.7.md) and the nav badge (v1→v1.7) — to match IntentFile/intent-specification#63, which cuts version 1.7.Version number only. The site's spec pages themselves are still at the 1.5 catch-up (#29) and do not yet carry the 1.6 or 1.7 constructs; that content catch-up is a separate change.
🤖 Generated with Claude Code