title: Is it possible to ignore the dependency hash validation of just one module (or registry)?
body: <p>The <code>yarn.lock</code> file saves all the dependencies versions and the hashes of the modules. I know that I can globally disable this hash checking with the option <code>--skip-integrity-check</code>.</p>
  
  <p>We have an internal module that is continually developed. The dependency is really of a snapshot package. When it is updated, it fails in our continuous integration environment because the updated package hash is different of the yarn.lock saved hash. </p>
  
  <p>Is it possible to disable the integrity check just for a specific module? </p>
  
  <p>I'll accept the answer even if it tells how to disable the check for all the modules of a specific registry. </p>
  
  <p><strong>Update:</strong> My problem is that my continuous integration server job is breaking when the dependency is updated, even if there's no modification in my code. These are spurious failings and I want to stop them. </p>
  
  <p><strong>Update 2:</strong> The accepted solution is really a hack to solve a problem in a usual development workflow. There is an <a href="https://github.com/yarnpkg/yarn/issues/2314" rel="noreferrer">issue open for Yarn in GitHub</a> to fix this problem. </p>