Skip to content

diff/build: change-reporting gaps #80

Open

Description

@Kinflou

Found while working out the compatibility rules (tracking issue in core).

  • history::load_schemas loads every tree entry, dep_* subtrees included, so comline diff on a package with dependencies treats a dependency as one of its schemas.
  • comline diff reports no bump and no config changes. It only runs analyze_schema_changes, pairwise by index.
  • comline build never prints config or dependency changes. A bump caused only by those prints "version X (no changes)".
  • No machine-readable output for build or diff (--json exists only on targets --features).
  • Nothing can fail a build on a breaking change. Is a --deny-breaking (or a CI-oriented comline diff --check) wanted?

Activity

  1. added
    bugSomething isn't working
    toolingCLI, language server, editor
    on Oct 18, 2026
  2. Kinflou commented on Oct 20, 2026

    @Kinflou
    MemberAuthor

    Decided 2026-10-20 (ComlineProject/docs#64): failing on a break is a setting, versioning.allow = major | minor | patch (default major), plus comline build --deny <level> to override it for one run. A build whose computed bump exceeds it fails, listing the responsible changes.

  3. added
    1.0-blockerMust be done before the 1.0 announcement (docs conduct/readiness.md)
    P1Next
    on Oct 31, 2026
  4. added this to the 1.0 milestone on Oct 31, 2026
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

    1.0-blockerMust be done before the 1.0 announcement (docs conduct/readiness.md)P1NextbugSomething isn't workingtoolingCLI, language server, editor

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions