Skip to content

Deprecate resolving an unstable graph #29936

@jvandort

Description

@jvandort

Expected Behavior

When the resolution engine encounters an unstable graph, it emits a deprecation warning. Eventually, these graphs should fail with an error. The warnings and errors should include details on how to resolve the unstable graph, for example by telling the user to add a dependency constraint

Current Behavior (optional)

No response

Context

There are two scenarios we should deprecate:

  1. Unstable version selection
  2. Selector reuse instability

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions