I have a build reporting that the yarn lock file needs to be updated, but if I run it locally there ...

# javascript

[alec]

I have a build reporting that the yarn lock file needs to be updated, but if I run it locally there are no changes. Conversely in a separate PR it goes green on CI, but if I run the same build locally it asks me to update the yarn lock.

This makes me think the actual output of the yarn lock file is different locally vs CI in my setup - wondering if anyone has run into this or if anyone has any ideas as to why this is happening?

[Derek Ellis]

If this is about that SQLDelight job, it's weird that it only happens with the multiplatform plugin and not the js plugin!

[alec]

yes its about SQLD

[alec]

im wondering if we should just disable this behavior or have it warn instead of fail the build

[andylamax]

I like that it fails the build

[Andrew]

Are the same yarn versions used in both environments?

[Derek Ellis]

The yarn version is whatever the Kotlin gradle plugin provides (so yes, presumably)