paket update makes the dependency graph in paket.lock go back and forth between the same two sets of framework restrictions for package with no change

When calling "paket\paket update <PaketID> --version <version> --redirects" for packages that have no relation to Confluent.Kafka, the dependency graph for Confluent.Kafka (2.0.2) in paket.lock goes back and forth between the same two sets of framework restrictions for the transitive packages. It doesn't happen every time, it happens to seemingly random people from the team, it's not fixed like set 1 happens to person 1 and set 2 happens to person 2, we can have both sets of restrictions happen to the same person.

For example i call "paket\paket update PackageA --version 1.0.2 --redirects", it updates the package version in paket.lock for this package but changes the framework restrictions for the transitive packages of Confluent.Kafka (2.0.2) from set 1 to set 2. After I check in my paket.lock file, a colleague calls "paket\paket update PackageB --version 1.0.1 --redirects", again it updates the package version in paket.lock for this package but changes the framework restrictions for the transitive packages of Confluent.Kafka (2.0.2) from set 2 to set 1. I can have someone else check in before me a paket.lock file with restrictions set 2 and when calling "paket\paket update PackageC --version 1.0.1 --redirects" change framework restrictions for the transitive packages of Confluent.Kafka (2.0.2) from set 2 to set 1. Again we can call "paket\paket update <PaketID> --version <version> --redirects" and in paket.lock get only the update of the specified package, with not changes for Confluent.Kafka (2.0.2).

paket.exe, paket.dependencies, paket.lock, Nuget.config are all under source control so they are the same for everyone.

There is no error with either set of framework restrictions for the Confluent.Kafka (2.0.2), it all works the same.

I know paket update resolves or "recalculates" the dependency graph each time it is called, deletes the old one and doesn't keep the last solution, but seeing as all input parameters for Confluent.Kafka (2.0.2) are the same shouldn't the output be the same? What determines when there are going to be changes for the framework restrictions for Confluent.Kafka (2.0.2) and when there won't be? And is there a way to stop this behaviour and have one final set of restrictions?

These are the two diferent sets of framework restrictions for Confluent.Kafka (2.0.2)