Skip to content

feat(extensions): engines ranges with several comparators - #1630

Merged
ZhuchkaTriplesix merged 1 commit into
devfrom
issue/engines-ranges
Oct 16, 2026
Merged

ZhuchkaTriplesix merged 1 commit into
devfrom
issue/engines-ranges

Conversation

@ZhuchkaTriplesix

Copy link
Copy Markdown
Member

Found with the first real registry record: the ClickHouse driver declares engines.querya_desktop as >=0.4.0 <3.0.0, and engineRangeAllows could not read it (only >=x.y.z and ^x.y.z), so the extension was visible on every version and the tester warned about an unsupported range.

  • engineRangeAllows: space-separated comparators that must all hold (>=, >, <=, <, =, ^), and * alone for any version. Anything it still cannot read (~0.4, ||, a bare version, * <3.0.0) is null: shown with a warning, not guessed.
  • The warning text says what is accepted. HostVersion gets <=.
  • Tests for each comparator, caret, the ClickHouse range, *, unreadable ranges and the two warnings. Docs (extension-manifest.md) and CHANGELOG.

The registry gets a matching check (refuse a range the app cannot read) in its own repository. Not run locally; CI decides.

….0.0)

The ClickHouse driver declares >=0.4.0 <3.0.0, which engineRangeAllows could not
read (only >=x.y.z and ^x.y.z), so the extension showed on every version. Space
separated comparators now all have to hold; * means any version; a range that is
still not understood stays null (shown with a warning) instead of a guess.
@ZhuchkaTriplesix
ZhuchkaTriplesix merged commit cfab2fa into dev Oct 16, 2026
13 checks passed
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