[CI] Should update dependencies cache when local package as dependencies mutates

[prastoin]

Introduction

When updating several packages within a same PR, a introducing a mutation, this might bring cache invalidation as in twentyhq/twenty#10699

Twenty-shared is now a dependency, which means it will be cached along node-modules, when updating and rebuilding it it does not change the lockfile which result in not updating the cache

Solutions:

Semver

• Follow not a * version but a specific ^ version, this should update lockfile this means we need to upgrade the sub dep version each time ...

To be thinked further !

Changed files

Look in latest commit if a local package as been modified, if yes than invalidate cache

[prastoin]

I think the initial issue is related to nx not detecting a diff in build due to import path update that resulted in the same transpilation 🤔
at least something very specific cannot reproduce the error again either
Closing this from now

[prastoin]

Update

I'm just a fool and spent 2 hours trying to debug something that wasn't a caching issue but a human man
Also useless to do not cache node_modules local packages as they only contain symlink to corresponding packages folders

I'm a fool