chore: minor tuning of GHA build

[ssbarnea]

Description

This should address error seen on https://github.com/streetsidesoftware/cspell-dicts/actions/runs/11125090808/job/30912037317?pr=3446#step:3:67 which should have not happen, especially as the package.json and its lock were not touched by that change.

References

• Any source references.

Checklist

• By submitting this pull-request, you agree to follow our Code of Conduct
• Verify that the title starts with the correct prefix:
  • fix: - for minor changes like adding words or fixing spelling issues.
  • feat: - for a significant change like adding a whole new set of words to a dictionary.
  • feat!: - for breaking changes, like file format or licensing changes.
  • chore: - for changes that do not impact the content of dictionaries.

[Jason3S]

Thank you for the heads up on the broken build.

[ssbarnea]

I made it draft as I will use to modify the actions to make use of the file.

One thing that I observed is that pnpm has the bad habit of updating the lockfile by default on install, that being different than npm and yarn, which need an extra argument to refresh the lock. pnpm goes the other way around and requires the switch to make it use the file.

Based on version of node being used (18 or 20), it seems that it updates two types files, very unlikely to really break the code but enough to cause churn.

I guess that we need to be sure that the lock file is produced with minimal supported version of node.

[Jason3S]

I made it draft as I will use to modify the actions to make use of the file.

One thing that I observed is that pnpm has the bad habit of updating the lockfile by default on install, that being different than npm and yarn, which need an extra argument to refresh the lock. pnpm goes the other way around and requires the switch to make it use the file.

Based on version of node being used (18 or 20), it seems that it updates two types files, very unlikely to really break the code but enough to cause churn.

I guess that we need to be sure that the lock file is produced with minimal supported version of node.

There is a workflow (update-dependencies) that will fix the pnpm-lock.yaml file. There is a bit of churn, but it settles on the workflow version.