Skip to content

chore: use minimum-only host compatibility - #18

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

Applies the bitty#2462 minimum-only host compatibility directive: the manifest
declares bitty = ">=0.0.24" with no upper bound, so newer hosts (0.0.x and
0.1+) are no longer refused by a manifest ceiling. plugin-api = "^1.0" is
unchanged.

New line: bitty = ">=0.0.24".

Changes

  • bitty-plugin.toml: [compat].bitty >=0.0.24,<0.1 → >=0.0.24, and the
    comment records the minimum-only contract.
  • README.md: prerequisites, the E_INCOMPATIBLE cause/remedy, and the
    Scope/Compat sections follow the new minimum.

Verification

  • just install then just check passes locally: Prettier, markdownlint,
    metadata, hygiene, portable-path gate, bitty-plugin-lint, luaparse plus the
    fail-closed control, docs check, and the behavior suite (49 passed).

Priority: P1 | Area: plugin | Labels: chore, P1, area:plugin | Milestone: v0.1.0 | RFC: n/a | Task: n/a (bitty#2462)

bitty#2462: declare `bitty = ">=0.0.24"` with no upper bound in `[compat]`
and keep `plugin-api = "^1.0"`. README prerequisites, `E_INCOMPATIBLE`
guidance, and Scope/Compat sections follow the same minimum-only contract.
@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 132a350 into main Oct 22, 2026
7 checks passed
@Xuepoo
Xuepoo deleted the cmd/compat-minimum-0026 branch October 22, 2026 07:33
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