Resetting cache when packages dependencies have changes

[kickbk]

I noticed that if I update dependencies in one of the packages, while I previously ran a build via GitHub actions, then next time I deploy, it will use the outdated cache stored on GitHub and this will finally generate an app on EAS using the old packages dependencies.
I know we invalidate Metro cache when env vars change, but what about the cache that needs to be invalidated when updating package dependencies?

Currently metro.json has:

"build": {
  "dependsOn": ["^build"],
  "outputs": [
    ".next/**",
    "build/**",
    "node_modules/.cache/metro/**"
  ],
  "env": [
    ...
  ]
},

Or maybe I'm missing something, if so, could you please let me know what?

[byCedric]

Technically speaking, that should have been covered by Metro itself. Metro's own caching should have detected that files were changed, and it needs to transpile the package again. I'm not sure what kind of change you made, but if you have an example, I'd be happy to debug it.

What you can do for now to avoid this in the future is to disable the cache in GitHub Actions. That way, you are always sure you are building from the source without possible incorrect caches. It might slow down your CI a bit, but I think stability should be preferred over performance in CI.