Skip to content

chore: use minimum-only host compatibility - #20

Merged
Xuepoo merged 1 commit into
mainfrom
cmd/compat-minimum-0026
Oct 22, 2026
Merged

Xuepoo merged 1 commit into
mainfrom
cmd/compat-minimum-0026

Conversation

@Xuepoo

@Xuepoo Xuepoo commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Summary

Make the manifest host compatibility minimum-only, per the owner directive in bitty-terminal/bitty#2462: compat.bitty no longer carries an upper bound, so later host releases stay eligible without a plugin manifest edit. The Plugin API range (plugin-api = "^1.0") is unchanged and remains the breaking-change boundary.

  • bitty-plugin.toml: bitty = ">=0.0.24" (was >=0.0.24,<0.1)
  • README.md: install prerequisite and scope text updated to the minimum-only range
  • Tests updated where they asserted the old range: the range is pinned to the floor, later hosts must be admitted, and pre-floor hosts must still be rejected

Verification

  • just check — passed (manifest lint, formatting, Markdown lint, Lua parse/control, behavior suite)

Refs bitty-terminal/bitty#2462

Priority: P1 | Area: plugin | Labels: chore,area:plugin,P1 | Milestone: v0.1.0 | RFC: OQ-012 | Task: CTX-1446

@Xuepoo Xuepoo added this to the v0.1.0 milestone Oct 22, 2026
@Xuepoo Xuepoo added chore P1 area:plugin Plugin manifest and runtime surface labels Oct 22, 2026
@Xuepoo
Xuepoo merged commit cb894b4 into main Oct 22, 2026
7 checks passed
@Xuepoo
Xuepoo deleted the cmd/compat-minimum-0026 branch October 22, 2026 07:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:plugin Plugin manifest and runtime surface chore P1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant