fix: Move V installation out of current working directory

[cadamsdev]

Notable changes

• Moved the V installation to the home directory instead of the current working directory.
• Cleaned up the CI workflow
  • cache npm (faster npm ci)
  • use matrix strategies instead of separate jobs
  • updated version argument to 0.5.1
  • removed redundant use-latest-stable job

Fixes #9, #7, #6

Before

After

[JalonSolov]

The CI is loading a positively "ancient" version of V, so that is likely the cause of the failure. The CI is also only using node 20, rather than something later... no idea if that's a problem or not.

Also, did you bump the version in your changes?

[cadamsdev]

Hey @JalonSolov

The CI is loading a positively "ancient" version of V, so that is likely the cause of the failure.

I bumped it to the latest stable version "0.5". Hopefully that fixes it. 🤞

The CI is also only using node 20, rather than something later... no idea if that's a problem or not.

That shouldn't cause any issues. I'll create a separate PR to update the node version. 👍 We should use the latest Node LTS version (Node v24).

Also, did you bump the version in your changes?

We don't need to bump it. Just create/republish the major tag. Since these changes are backwards compatible, I recommend updating the v1 tag (common practice in GitHub Actions). No need for minor tags like v1.1, v1.2, etc.

[JalonSolov]

V 0.5.1 was just released, so there is that.

Personally, I'd rather just use latest, since V still changes quite often, and even here we've just seen how anyone using this action was getting an "ancient" version because the CI wasn't being updated. :-\

[cadamsdev]

V 0.5.1 was just released, so there is that.

Personally, I'd rather just use latest, since V still changes quite often

We can't use latest. The job requires us to pass in a specific version to test the version argument.

anyone using this action was getting an "ancient" version because the CI wasn't being updated. :-\

Users of this action won't get an "ancient" version of V. That only affects the workflow in this repo because the version was hardcoded to an older version. (This repo hasn't been updated in 2 years)

Here's the scenarios

If the version is not specified, the action uses v version 0.5.1

- name: Setup V
   uses: vlang/setup-v@v1.4

Setting check-latest uses v version 0.5.1

- name: Setup V
   uses: vlang/setup-v@v1.4
   with:
     check-latest: true

Setting stable uses v version 0.5.1

- name: Setup V
   uses: vlang/setup-v@v1.4
   with:
     stable: true

Setting check-latest and stable uses v version 0.5.1

- name: Setup V
   uses: vlang/setup-v@v1.4
   with:
     check-latest: true
     stable: true

Setting explicit version will use that version e.g

- name: Setup V
   uses: vlang/setup-v@v1.4
   with:
     version: weekly.2026.08

Uses v version weekly.2026.08

The action seems to be working correctly.