Repository navigation
fix(manifest): admit Bitty 0.0.24 - #15
Merged
Merged
Conversation
This was referenced Oct 19, 2026
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.
Closes #14
Change
compat.bittywas>=0.5,<1.0, an aspirational floor that rejects every 0.0.x host (install exits 4 before activation). It is now>=0.0.24,<0.1, matching the verified 0.0.24 host and the range already used bypaletteandbar. No other manifest field changes.tests/verify-live-parity.test.tspinned the old range in its manifest assertion, so that single assertion is updated with the manifest; plugin behavior is untouched.Verification
just check— pass (fmt, markdown, metadata, hygiene, paths, manifest, lua, lua-control, 51 tests)bitty-plugin-lint bitty-plugin.toml— valid (0 errors)<0.1ceiling.