I'm having issues with `yarn.lock` checks. I've just updated an npm dependency, run `gradle kotlinU...

# javascript

[Edoardo Luppi]

I'm having issues with yarn.lock checks.

I've just updated an npm dependency, run gradle kotlinUpgradeYarnLock, and committed + pushed the yarn.lock changes.
Locally builds fine, on Jenkins it returns:

00:02:51.294  FAILURE: Build failed with an exception.
00:02:51.294  
00:02:51.294  * What went wrong:
00:02:51.294  Execution failed for task ':kotlinStoreYarnLock'.
00:02:51.294  > yarn.lock was changed. Run the `kotlinUpgradeYarnLock` task to actualize yarn.lock file

Am I supposed to run kotlinUpgradeYarnLock on the Jenkins pipeline too, or should it work straight away? I don't recall this issue in the past.

[Edoardo Luppi]

I've run kotlinUpgradeYarnLock manually on the CI disk, and the yarn.lock file has remained exactly the same.
But now it doesn't complain? Mmmh, I don't get it

[hfhbd]

Maybe different line endings?

[Edoardo Luppi]

@hfhbd the plugin seems to check line by line, so the line endings get discarded

[andylamax]

kotlin 2.0.0 eeeh?

[Edoardo Luppi]

@andylamax no no, 1.9.22

[andylamax]

I started getting the error when I jumped from 1.9.21 to 2.0.0. I never used 1.9.22.

But since that jump, if have had to run kotlinUpdateYarnLock before any task involing kotlin/js for the task to execute successfully