Skip to content

Compat baseline 5/5: publish a distinct, traceable supported-baseline version #135

Closed

Description

@cchacs

Effort: S

Part of #102. Last: depends on 1/5, 3/5 and 4/5. This is a maintainer decision plus a release action.

Version strings are reused across many commits, so a user cannot tell which build is compatible. Publish a baseline that can be identified from its release or commit.

Scope

Acceptance criteria

  • A user can identify a compatible build from its release or commit.
  • An incompatible feature explains its missing requirement before use.
  • Tested host and plugin revisions are recorded in the matrix.

Out of scope

Back-certifying older builds.

Activity

  1. pullfrog commented on Oct 2, 2026

    @pullfrog
  2. cchacs commented on Oct 2, 2026

    @cchacs
    CollaboratorAuthor

    @itsjustroxi this sub-issue (of #102) is a maintainer decision plus a release action: choose the supported baseline. #102 names e5339c0 or a tested descendant as the candidate (not yet certified), and the baseline needs a distinct, traceable version, not a reuse of 0.3.0-alpha.2. It is last in the order, after the compatibility matrix, the minHost work and the tests, so there is nothing to decide yet; this is a heads-up.


    Generated by Claude Code

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

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions