Skip to content

Lack of dependency constraints in old versions cause build failures #73

@TravisCardwell

Description

@TravisCardwell

The lack of dependency version constraints in old versions of Ginger can cause those versions to be selected for a build plan and fail.

I ran into this issue when I published queue-sheet-0.7.0.2 on Hackage. The build failed with a DependencyFailed error. The build report shows that GHC 8.10.2 was used, and it looks like ginger-0.8.2.0 was selected so that the latest versions of aeson and optparse-applicative could be used. This version of Ginger does not specify aeson version constraints, but it fails to build with the selected aeson-2.0.3.0.

Perhaps package revisions should be created for older versions of Ginger to add appropriate dependency version constraints and ensure that they are not selected with incompatible dependency versions?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions