Skip to content

WHY - Help developers know why a package can't be updated to latest version #31

@omarlopesino

Description

@omarlopesino

Currently when a composer package can't be updated it shows a message indicating that there are restrictions. It would be nice to add additional information that helps developers to know why the package can be updated.

Proposed resolution

Showing the full error message may pollute the drupal updater output, but we can suggest the user how to debug it. Add a message proposing running the composer require command with the --dry-run option. SOmething like this:

For more information, run: composer require vendor/package:^<latest_version> -W --dry-run

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions