[feature] Strict mode for lockfile creation that fails if no PREV is available

We maintain our own remote with custom packages and use lockfiles to ensure reproducible builds. When a developer wants to update a package or add a new one, they’re expected to use our CI/CD infrastructure to publish a new conan package to our remote and then update the lockfiles on the repos that consume conan packages. This usually works but there is a frequent issue: sometimes when a lockfiles gets re-created we end up with a node that has no prev on it. This is usually because the dev did somenthing wrong on the conanfile. This situation is hard to catch since our lockfiles are pretty big and not all of our developers are big on conan, so they don’t know what they’re looking at. In our case if you commit a lockfile that has (at least) one node without PR, the CI/CD builds that validate PRs fail since there’s no package available upstream and we don’t use --build=missing.

I was wondering if we could add a --strict switch to the lockfile creation command that errors out if there is no package available for a given reference, that way we can catch this issues ASAP.

Thanks!

[ericriff]

Awesome! Exiting times ahead of us. Thanks for the info 😃

[memsharded]

We are about to do 2.0-beta.3, it is getting ready quickly, I’d expect a couple of releases more until GA. It might require a bit more time to let ConanCenter catch-up and update a reasonable amount of recipes, but otherwise the Conan client will be ready soon.