Default policy seems to downgrade my stability level?

[martinbonnin]

If I'm reading the README right:

There's only one predefined policy at the moment, which is stability-level. This policy will only select an update if its stability is greater than or equal to the stability of the current version.

This means that if you're using a beta version, alpha versions won't be suggested for you, and so on

But then with the following file:

[versions]
apollo = "4.0.0"

[libraries]
apollo-runtime = { group = "com.apollographql.apollo", name = "apollo-runtime", version.ref = "apollo" }

Caupain suggests updates to alpha versions:

$ caupain -i libs.versions.toml
Updates are available
Library updates:
- com.apollographql.apollo:apollo-runtime: 4.0.0 -> 5.0.0-alpha.2

I am using 1.6.0. Am I holding it wrong or is this a bug?

[bishiboosh]

stability-level is the only predefined policy, but it's not specified by default. If it's not activated in the config file or via the correct switch, the default policy is to not have any policy and notify of every update. Perhaps I should have stability-level as the default policy and allow a --policy=none switch to allow to disable it, wdyt ?

[martinbonnin]

Aaaah, that's what I was missing. Nitpicking but looks like there should be 2 predefined policies then?

• always
• stability-level

I'm not a fan of none as "always updating" is a policy so there is always one.

+1 for stability-level by default in all cases.

[bishiboosh]

I've just released a new version, but I'll do that for the next one.

[bishiboosh]

I've opened #59 to track this