Safe-updating prereleases

Mar 13, 2012 at 1:20 PM

When issue an Update-Package with both -Safe and -IncludePrerelease the latter seems to be ignored.

1.0.0 would be updated to 1.1.0-RC but not 1.1.0.

Is this intended behaviour?

Mar 13, 2012 at 3:48 PM

Yes, it's the intended behavior. 1.0.0 -> 1.1.0 would be considered a major and (potentially) breaking changes, and hence not safe.

Mar 13, 2012 at 4:09 PM

Then why would i want the 1.1.0-RC or 2.0.0-RC for that matter? 

Mar 13, 2012 at 9:39 PM

Yah, that is the artifact of our code whereby we consider any version smaller than 1.1.0 to be eligible for -Safe update, and 1.1.0-RC happens to be smaller than 1.1.0. Maybe we should re-consider this.

Mar 14, 2012 at 7:52 AM

Thank you for the reply.

I can confirm that i works as you have described, though it would make more sense if 1.0.0 would not safely upgrade to 1.1.0-RC.

Mar 14, 2012 at 6:11 PM

I agree.  -Safe should act like the help says it should "upgrade to newer versions with the same Major and Minor version component.". 1.0.0 to 1.1.0-RC, doesn't feel like the same major and minor version.

Mar 14, 2012 at 6:12 PM

I think this is unarguably a bug.

Mar 14, 2012 at 6:15 PM

filed to track it.