fix(ci): integration tests pick up local .dtvem/runtimes.json

[CalvinAllen]

Summary

Integration tests run from the cloned repo directory, which contains a local .dtvem/runtimes.json config file. This causes the current command to read versions from the local config instead of the global config set by the tests.

Problem

The repo has a local config at .dtvem/runtimes.json:

{
  "node": "22.0.0",
  "python": "3.8.9",
  "ruby": "3.3.9"
}

When tests set a global version (e.g., dtvem global node 20.18.0) and then run dtvem current node, the local config takes precedence, returning 22.0.0 instead of 20.18.0.

Solution

Run integration tests from a directory outside the repo workspace (${{ github.workspace }}/../dtvem-test-workspace) to avoid picking up the local .dtvem/runtimes.json.

Affected Workflows

• integration-test-node.yml
• integration-test-python.yml
• integration-test-ruby.yml

Related

• Closes fix(current): command reads wrong version on Windows #135 (this was the root cause)