fix(babel-jest): add process.version chunk to the cache key

[mrazauskas]

Fixes #12117

Summary

As it is pointed out in the issue, currently babel-jest does not invalided Jest’s cache in case if users downgrade (or upgrade) Node’s version. (jest --clear-cache should be used.)

Seems like it may be a good idea to add process.version as one of cache key chunks. Should the string include only major / minor or full version? Looking at other chunks of the cache key, I went for full version. Not sure if this can be an issue for performance?

Test plan

I added a simple unit for getCacheKey function.

[codecov-commenter]

Codecov Report

Merging #12122 (d3b85e3) into main (5640f88) will increase coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main   #12122      +/-   ##
==========================================
+ Coverage   67.65%   67.71%   +0.05%     
==========================================
  Files         328      328              
  Lines       16990    16990              
  Branches     4817     4817              
==========================================
+ Hits        11495    11505      +10     
+ Misses       5462     5452      -10     
  Partials       33       33              

Impacted Files	Coverage Δ
packages/babel-jest/src/index.ts	86.48% <ø> (+13.51%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5640f88...d3b85e3. Read the comment docs.

[SimenB]

thanks!

New syntax is added in minor versions, so we should at least have that. I think full makes sense as well swapping node versions often doesn't seem likely to me, so I don't think there's a performance issue here

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.