Skip to content

Release 1.0.0#16

Merged
topkoa merged 1 commit into
mainfrom
release/1.0.0
Jul 6, 2026
Merged

Release 1.0.0#16
topkoa merged 1 commit into
mainfrom
release/1.0.0

Conversation

@topkoa

@topkoa topkoa commented Jul 6, 2026

Copy link
Copy Markdown
Collaborator

Summary

Cuts the 1.0.0 stable release. All the accumulated spec + best-practices work has merged to main under [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] now v1.0.0...HEAD, added [1.0.0] link).
  • spec/plugin-spec-v1.md: Specification version 0.1.0 → 1.0.0, Status Draft → Stable.
  • README.md: version table 0.1.0 → 1.0.0, status Draft → Stable.

On merge

The release workflow cuts the v1.0.0 tag + GitHub Release automatically (release notes = the ## [1.0.0] section), since no v1.0.0 release exists yet. No manual tagging needed.

Checks

tools/check_versions.pyversions consistent: 1.0.0; mkdocs build --strict passes.

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

  • Documentation
    • Marked the specification and companion guide as stable in version 1.0.0.
    • Updated the README and spec metadata to reflect the new stable release.
    • Expanded the changelog with the full set of documented platform and best-practice updates.
    • Refreshes release links so future changes compare against v1.0.0.

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>
@coderabbitai

coderabbitai Bot commented Jul 6, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 237c22bc-6b3f-4af0-8009-979c9bdf0579

📥 Commits

Reviewing files that changed from the base of the PR and between 1859e0e and 2bd612b.

📒 Files selected for processing (3)
  • CHANGELOG.md
  • README.md
  • spec/plugin-spec-v1.md

📝 Walkthrough

Walkthrough

This 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.

Changes

1.0.0 Stable Release Documentation

Layer / File(s) Summary
Changelog entry for 1.0.0 release
CHANGELOG.md
Adds the [1.0.0] - 2026-07-06 section header and description, an extensive ### Changed list covering capability/schema, client contract, and best-practices guide updates, and updates the compare links at the bottom of the file.
Version and status metadata updates
README.md, spec/plugin-spec-v1.md
Bumps the Specification version from 0.1.0 to 1.0.0 and Status from Draft to Stable in the plugin spec metadata table (README) and the spec document header.

Estimated code review effort: 1 (Trivial) | ~5 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely summarizes the main change: cutting the 1.0.0 release.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/1.0.0

Comment @coderabbitai help to get the list of available commands.

@topkoa
topkoa merged commit 2995351 into main Jul 6, 2026
7 of 8 checks passed
@topkoa
topkoa deleted the release/1.0.0 branch July 6, 2026 04:54
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