paket outdated should optionally evaluate version constraints #183

Activity

1. agross

   added

   enhancement

   on Sep 29, 2014
2. forki commented on Sep 29, 2014

   

   forki

   on Sep 29, 2014

   Member

   More actions

   so --strict would be the mode we are currently running.
   In the new default mode we would assume no version requirements are given in dependencies file and basically all is >= 0!?

   How does this relate to #184?
3. agross commented on Sep 29, 2014

   

   agross

   on Sep 29, 2014

   ContributorAuthor

   More actions

   paket.dependencies:

   nuget Foo ~> 1.2 prerelease
   nuget Bar ~> 1.2
   

   paket outdated:

   • check for new versions of Foo, 0 <= x
   • check for new versions of Bar, 0 <= x

   paket outdated --strict

   • check for new versions of Foo, 1.2 <= x < 2, including all prereleases
   • check for new versions of Bar, 1.2 <= x < 2

   paket outdated --pre

   • check for new versions of Foo, 0 <= x, including all prereleases
   • check for new versions of Bar, 0 <= x, including all prereleases

   paket outdated --strict --pre

   • check for new versions of Foo, 1.2 <= x < 2, including all prereleases
   • check for new versions of Bar, 1.2 <= x < 2, including all prereleases
4. forki

   closed this as completedin 3e72d1eon Sep 29, 2014
5. forki

   added 2 commits that reference this issue on Oct 30, 2015

   Create regression test for #183

   f017fb3

   Create regression test for #183

   d53e112
6. fpellet

   added a commit that references this issue on Oct 11, 2026

   test: run on net10.0 the integration tests that only net461 covered

   ...

   726d776