Better deps handling

[vicb]

The pubspec.yaml reads as follow

  di: ">=0.0.40 <2.0.0"
  stack_trace: ">=0.9.1 <2.0.0"

You can introduce a BC break by running a pub update because di and stack_trace can have a BC break. According to semver, the constraints should be:

• `>=0.m.p <0.m+1.0' for pre 1.0 pkgs,
• '>=M.m.p <M+1.0.0` for post 1.0

[luizmineo]

Thanks for pointing me this out. These two packages have recently reached the 1.0 version, so I widened their constraints to allow the users to get the latest versions. According to their changelogs, there is no break changes between the pre-1.0 and 1.0 versions, but I will update the pubspec.yaml as soon as other core packages, like unittest and angular, updates their pubspec.yaml as well.

[vicb]

We haven't done a good job on using semver for di / route_hierarchical and it has caused troubles (I work for the angular.dart team and contribute to those).

In the future we will follow semver in a stricter way. You would save our users from troubles by doing

 di: ">=1.0.0 <2.0.0"
 stack_trace: ">=0.9.1 <0.10.0"

[vicb]

Sorry, my message is not very clear:

• I ack that your versionning constraints are ok because any version between your min and max have no BC breaks,
• I think using constraints which are meaningful in a semver way is a good way to educate users.

[luizmineo]

No worries. I understand your point and I agree with you. I plan to update the pubspec to follow the semver, and I just didn't it yet because there are some packages on pub that are still using the pre-1.0 versions, and I don't want to cause trouble to users that depends on them, neither prevent other users to update to the latest versions.

[Pacane]

Not a problem anymore.