Skip to content

paket pack - unexpected 3rd party version constraint when not using --lock-dependencies  #3910

Description

@Flohack74

Description

A paket pack command should create a nuget package that will enforce a certain minimum version (but not pinned) of a 3rd party dependency.

Repro steps

  1. Specify the 3rd party dependency with e.g. ~> 28.3 operator
  2. Do a paket pack without --lock-dependencies

Expected behavior

The resulting nuget package has a restriction to at e.g. >= 28.3.0 < 29.0.0

Actual behavior

The resulting package only specifies a restriction of ≥ 0.0.0

I did not remember to have this it with other constraint operators, maybe this is only happening with the twiddle wakka operator?

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions