docs: bump install snippet to 0.1.1#10
Conversation
Tracks the latest release tag so new adopters land on the version that ships the SwiftWebServer 0.3.1 memory fixes by default. Existing `from: "0.1.0"` declarations already resolve to 0.1.1 on swift package update; this is just for the documented floor.
Plugin manifest versions intentionally NOT bumped — they only change when the plugin's capabilities change (new skills, commands, hooks, MCP servers, behavior changes in existing components). A from: version reference inside SKILL.md is content drift, not a capability change. Bumping the manifest would prompt every installed user to "update" a plugin that gives them nothing new — worse UX than leaving them alone.
|
@claude review this PR |
|
Claude finished @atom2ueki's task in 38s —— View job PR Review
Summary: This is a clean, two-file docs-only change bumping the Swift Package Manager minimum version floor from Changes Reviewed
AssessmentCorrectness: Both snippets are updated consistently — no drift between the two docs. The version bump is accurate and aligns with the SwiftWebServer 0.3.1 dependency bump landed in #9. Rationale: Pointing new adopters at Minor observation: The PR title says "bump README install snippet" but Verdict: ✅ LGTM — trivial docs update, no behavioral change, both install snippets correctly updated. |
atom2ueki
changed the title
1 participant
One-line README change:
from: "0.1.0"→from: "0.1.1"in the install snippet so new adopters land on the version that ships the SwiftWebServer 0.3.1 memory fixes by default.Existing
from: "0.1.0"declarations already resolve up to 0.1.1 onswift package update(semver allows it within the same major), so this is purely a documented-floor update — no behavior change for existing consumers.No other staleness found in this pass:
initpattern).(Trivial docs change, no AI reviewer triggers — self-merge once CI lights up.)