feat(node-ci): forward cache-dependency-path to setup-node

[WomB0ComB0]

Summary

Polyglot repos with a lockfile outside the repo root couldn't adopt this reusable — actions/setup-node bailed with Dependencies lock file is not found because the reusable didn't accept a cache-dependency-path input.

Surfaced during resq-software/viz PR #58 adoption attempt. Viz's client pipeline (src/ResQ.Viz.Web/package-lock.json) currently uses a hand-rolled inline job because of this gap; once this lands + the viz ref pin bumps, it can switch to the shared reusable.

Changes

node-ci.yml

• New optional input cache-dependency-path: string (default "").
• Forwards to the actions/setup-node step's cache-dependency-path key.

required.yml

• Pass-through input node-cache-dependency-path so consumers routing through the org aggregator (most of them) can set it.

Backwards compatibility

Default is "". When unset, actions/setup-node treats the key as absent and falls back to repo-root lockfile detection — exactly the pre-PR behaviour. No current consumer needs updating; this only enables new adoption patterns.

Verification

• ruby -ryaml parses both YAMLs after the change
• node-ci.yml inputs: [... working-directory, cache-dependency-path, install-cmd, ...]
• required.yml node-* inputs: [..., node-build-cmd, node-cache-dependency-path]

Test plan (follow-up in viz)

Once merged, viz's ci.yml can switch from the hand-rolled client job to:

client:
  uses: resq-software/.github/.github/workflows/node-ci.yml@<new-sha>
  with:
    package-manager: npm
    working-directory: src/ResQ.Viz.Web
    cache-dependency-path: src/ResQ.Viz.Web/package-lock.json
    install-cmd: npm ci --legacy-peer-deps
    typecheck-cmd: npx tsc --noEmit
    build-cmd: npx vite build

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Enhanced Node.js dependency caching in CI/CD workflows to support custom lockfile paths, enabling improved build performance for repositories with lockfiles in non-standard locations.

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 03fd0673-82ab-4004-bd3b-3f0ac60a0300

📥 Commits

Reviewing files that changed from the base of the PR and between 109c36b and 0dd3efc.

📒 Files selected for processing (2)

• .github/workflows/node-ci.yml
• .github/workflows/required.yml

---

📝 Walkthrough

Walkthrough

GitHub Actions workflow files updated to support flexible Node.js dependency lockfile path configuration. Added cache-dependency-path input to node-ci.yml and node-cache-dependency-path input to required.yml, enabling proper cache key generation for polyglot repositories with lockfiles in non-root directories.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow Configuration .github/workflows/node-ci.yml, .github/workflows/required.yml	Added cache-dependency-path and node-cache-dependency-path inputs respectively with default empty strings. Updated workflow steps to forward the cache path parameter through the workflow call chain to actions/setup-node for dependency caching.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A rabbit hops through workflows deep,
With cache paths now in tidy keep,
No more lockfiles lost in nested places—
Each polyglot repo finds its traces! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: adding and forwarding the cache-dependency-path parameter to setup-node in the node-ci workflow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/node-ci-cache-dep-path

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}