[unstable option] required_version

[scampi]

Tracking issue for required_version

[reynoldsbd]

Would it make sense for required_version to support SemVer semantics similar to Cargo dependencies? This would make it easier to use in cases where CI agents are updated automatically.

For instance, if somebody sets required_version = "1.4.36" but their CI agent is updated separately with a newer patch-release such as 1.4.37, currently their CI build would fail.

[tseli0s]

Why is this not stabilized yet?

[calebcartwright]

Why is this not stabilized yet?

#5365
#5367

[boozook]

There should be semver match instead of just eq, I suppose.

[Awayume]

There should be semver match instead of just eq, I suppose.

I think so too.

[ologbonowiwi]

There should be semver match instead of just eq, I suppose.

Hey guys, willing to help. Should I open a PR to it?

[ytmimi]

@ologbonowiwi thanks for offering to help. Before submitting a PR could you open an issue describing what you're planning to implement. I think it might be useful to discuss the approach before jumping in and working on this.

[ologbonowiwi]

#6063 opened @ytmimi. Can you check if it makes sense?

[ologbonowiwi]

And regarding the conditions:

• Is the default value correct ?
• The design and implementation of the option are sound and clean.
• The option is well tested, both in unit tests and, optimally, in real usage.
• There is no open bug about the option that prevents its use. (I've checked this one, no bugs open)

Which of them still needs to be worked on?