ci(sync): update GitHub Actions

[indykiteone]

Automatically generated PR to sync GitHub Actions and related configs.

[Copilot]

Pull request overview

This PR updates the shared composite pre-commit GitHub Action to better align Node.js dependency caching with the package manager actually used by the repository (based on detected lockfiles).

Changes:

• Add lockfile-based detection to choose the appropriate actions/setup-node cache mode (npm/yarn/pnpm) and dependency path.
• Add validation logic around Node hook detection vs. presence of supported lockfiles.
• Wire setup-node to use the dynamically detected cache settings.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (2)

.github/actions/pre-commit/action.yaml:185

• actions/setup-node is configured with only node-version-file, but NODE_VERSION_FILE can be empty when a repo has Node hooks/lockfiles without a root package.json (e.g., workspace setups). Passing an empty node-version-file can cause the setup step to fail; add a fallback that sets an explicit Node version when NODE_VERSION_FILE is empty.

      uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0 - https://github.com/actions/setup-node/releases
      with:
        node-version-file: ${{ steps.action-prep.outputs.NODE_VERSION_FILE }}
        cache: ${{ steps.action-prep.outputs.NODE_PM }}
        cache-dependency-path: ${{ steps.action-prep.outputs.NODE_PM_LOCKFILE }}

.github/actions/pre-commit/action.yaml:102

• The grep -c / grep pipeline results are used to populate outputs, but grep returns exit status 1 when there are no matches; with the default GitHub Actions bash options (-e/pipefail), that can terminate the step even though a 0 count is expected. Consider making these greps non-fatal and defaulting the count to 0.

            echo "IS_TERRAFORM=$(grep -c "terraform" "$_CONFIG")"
            echo "IS_GOLANG=${IS_GOLANG:-$(grep -E "\<(go|golang)\>" "$_CONFIG" | grep -vEc "(language: go|gone|- repo)")}"

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

.github/actions/pre-commit/action.yaml:185

• actions/setup-node no longer sets an explicit Node version. When NODE_VERSION_FILE is empty (e.g., no package.json), the job will fall back to the runner’s preinstalled Node version, which can drift over time and make pre-commit runs less reproducible. Consider adding an explicit fallback version (keeping the previous latest behavior) while still allowing node-version-file to override when present.

      with:
        node-version-file: ${{ steps.action-prep.outputs.NODE_VERSION_FILE }}
        cache: ${{ steps.action-prep.outputs.NODE_PM }}
        cache-dependency-path: ${{ steps.action-prep.outputs.NODE_PM_LOCKFILE }}

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

.github/actions/pre-commit/action.yaml:185

• actions/setup-node is now configured with only node-version-file. When NODE_VERSION_FILE is empty (e.g., no root package.json) or the file doesn’t contain an engines-based Node version, setup-node can fail because no Node version is specified. Consider keeping a safe fallback (e.g., node-version: latest) so Node hooks still work when a version file is absent or non-informative.

    - name: setup/node
      uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0 - https://github.com/actions/setup-node/releases
      with:
        node-version-file: ${{ steps.action-prep.outputs.NODE_VERSION_FILE }}
        cache: ${{ steps.action-prep.outputs.NODE_PM }}
        cache-dependency-path: ${{ steps.action-prep.outputs.NODE_PM_LOCKFILE }}

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (2)

.github/actions/pre-commit/action.yaml:102

• The bash snippet writing outputs to $GITHUB_OUTPUT has unescaped nested double-quotes in the command substitutions (e.g., grep -c "terraform" and grep -E "\<(go|golang)\>"), which will cause a syntax error when this step runs.

            echo "IS_TERRAFORM=$(grep -c "terraform" "$_CONFIG")"
            echo "IS_GOLANG=${IS_GOLANG:-$(grep -E "\<(go|golang)\>" "$_CONFIG" | grep -vEc "(language: go|gone|- repo)")}"

.github/actions/pre-commit/action.yaml:189

• actions/setup-node is always invoked with node-version-file sourced from NODE_VERSION_FILE, but NODE_VERSION_FILE is set only when package.json exists. If a repo has Node hooks + a supported lockfile but no package.json (or uses a different version file like .nvmrc), this will pass an empty path and likely fail the action.

    - name: setup/node
      uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0 - https://github.com/actions/setup-node/releases
      with:
        node-version-file: ${{ steps.action-prep.outputs.NODE_VERSION_FILE }}
        cache: ${{ steps.action-prep.outputs.NODE_PM }}
        cache-dependency-path: ${{ steps.action-prep.outputs.NODE_PM_LOCKFILE }}
      if: >-
        steps.action-prep.outputs.PRE_COMMIT_RUN == '1'
        && steps.action-prep.outputs.IS_NPM > 0
        && ((github.event_name != 'pull_request' && !steps.cache.outputs.cache-hit) || github.event_name == 'pull_request')