Skip to content

Conversation

@cdelfabbro
Copy link
Contributor

@cdelfabbro cdelfabbro commented Feb 12, 2025

Related to this thread, this PR evolves the node-module-cache to v2 bringing the support of multiple CPU architecture.

Do we have a depreciation process and a test process @jdassonvil?

Edit: I tested it here and the bali database migration is fixed, LGTM.

@cdelfabbro cdelfabbro force-pushed the feat/node-module-cache-cpu-architectures-array branch from b47310c to 1034654 Compare February 12, 2025 09:07
@cdelfabbro cdelfabbro force-pushed the feat/node-module-cache-cpu-architectures-array branch from 1034654 to f6f4c7c Compare February 12, 2025 09:12
@cdelfabbro cdelfabbro force-pushed the feat/node-module-cache-cpu-architectures-array branch from f6f4c7c to 4d87da9 Compare February 12, 2025 09:19
@jdassonvil
Copy link
Contributor

Do we have a depreciation process

usually we put the information in the workflow that it is deprecated (what you did) and communicate to teams that they should migrate (unfortunately you often end up doing it yourself)

and a test process

There's no easy way to test and automate github workflows modification, it's a bit painful. Let's hope github offer a better experience one day. Some tools allow you to write CI pipeline as code (like https://dagger.io/) so it's much easier to test but it's not as well integrated to Github as a native workflow.

Copy link
Contributor

@jdassonvil jdassonvil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@cdelfabbro cdelfabbro merged commit c69918e into master Feb 12, 2025
1 check passed
@cdelfabbro cdelfabbro deleted the feat/node-module-cache-cpu-architectures-array branch February 12, 2025 10:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants