Release 1.0.0#16
Merged
Merged
Conversation
First stable release. Move the accumulated [Unreleased] changes under a dated ## [1.0.0] heading, bump the version 0.1.0 -> 1.0.0 in the spec header and README table, flip the document Status from Draft to Stable, and update the CHANGELOG compare links. Merging this cuts the v1.0.0 tag + GitHub Release via the release-on-merge workflow. tools/check_versions.py: versions consistent at 1.0.0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: K. O. A. <topkoa@gmail.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThis PR documents the promotion of the plugin specification to version 1.0.0/Stable. CHANGELOG.md gains a new 1.0.0 release section detailing changes across the spec and best-practices guide, while README.md and spec/plugin-spec-v1.md have their version/status metadata updated accordingly. Changes1.0.0 Stable Release Documentation
Estimated code review effort: 1 (Trivial) | ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
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
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.
Summary
Cuts the 1.0.0 stable release. All the accumulated spec + best-practices work has merged to
mainunder[Unreleased]; this moves it under a dated## [1.0.0]heading and bumps the version everywhere the guard checks.Changes
CHANGELOG.md:[Unreleased]→## [1.0.0] - 2026-07-06(with a stable-release intro); compare links updated ([Unreleased]nowv1.0.0...HEAD, added[1.0.0]link).spec/plugin-spec-v1.md: Specification version0.1.0 → 1.0.0, StatusDraft → Stable.README.md: version table0.1.0 → 1.0.0, statusDraft → Stable.On merge
The
releaseworkflow cuts thev1.0.0tag + GitHub Release automatically (release notes = the## [1.0.0]section), since nov1.0.0release exists yet. No manual tagging needed.Checks
tools/check_versions.py→ versions consistent: 1.0.0;mkdocs build --strictpasses.Note
Flipped the document Status to Stable — the normative core (manifest, discovery, server/client surfaces) is stable; the parts that are still evolving (the client runtime API shape) remain explicitly marked "Host-versioned, not frozen" in the text. Say the word if you'd rather keep Status as "Draft" or use a different label.
🤖 Generated with Claude Code
Summary by CodeRabbit
1.0.0.v1.0.0.