Skip to content

Support pre-release versions as min and max versions #1494

Closed

Description

@benfrancis

Currently if you try to list 2.0.0-beta.1 as the minimum supported gateway version for an add-on in its manifest, the "Check changes" GitHub Action on this repo will fail because it doesn't recognise that as a valid version number according to the JSON schema.

Because the addon-proxy filters out 2.0.0-beta.1 as being older than 2.0.0 you can't just list 2.0.0 as the minimum version, so you have to list something older like 1.0.0 which might not be accurate.

Came across this problem with the Zigbee and X10-CM11 add-ons.

Activity

  1. moved this to Release Backlog in WebThings Gatewayon Nov 12, 2025
  2. added 2 commits that reference this issue on Dec 8, 2025
    a20ae9e
    0fbb63b
  3. moved this from Release Backlog to Done in WebThings Gatewayon Dec 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions