chore(deps): update actions/setup-node action to v4

[renovate[bot]]

This PR contains the following updates:

Package	Type	Update	Change
actions/setup-node	action	major	v3 -> v4

---

[!WARNING] Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

actions/setup-node (actions/setup-node)

### [`v4`](https://redirect.github.com/actions/setup-node/compare/v3...v4) [Compare Source](https://redirect.github.com/actions/setup-node/compare/v3...v4)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[keploynavigator[bot]]

Thanks for opening this pull request!

[cr-gpt[bot]]

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

[semanticdiff-com[bot]]

Review changes with SemanticDiff.

[sourcery-ai[bot]]

Reviewer's Guide by Sourcery

This pull request updates the GitHub Actions workflow to use the latest major version of the actions/setup-node action, moving from v3 to v4. This is a minor change that affects the CI/CD pipeline configuration.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Update actions/setup-node action from v3 to v4	Replace 'actions/setup-node@v3' with 'actions/setup-node@v4' in the workflow file	.github/workflows/package-v.yml

---

Tips and commands

#### Interacting with Sourcery - **Trigger a new review:** Comment `@sourcery-ai review` on the pull request. - **Continue discussions:** Reply directly to Sourcery's review comments. - **Generate a GitHub issue from a review comment:** Ask Sourcery to create an issue from a review comment by replying to it. - **Generate a pull request title:** Write `@sourcery-ai` anywhere in the pull request title to generate a title at any time. - **Generate a pull request summary:** Write `@sourcery-ai summary` anywhere in the pull request body to generate a PR summary at any time. You can also use this command to specify where the summary should be inserted. #### Customizing Your Experience Access your [dashboard](https://app.sourcery.ai) to: - Enable or disable review features such as the Sourcery-generated pull request summary, the reviewer's guide, and others. - Change the review language. - Add, remove or edit custom review instructions. - Adjust other review settings. #### Getting Help - [Contact our support team](mailto:support@sourcery.ai) for questions or feedback. - Visit our [documentation](https://docs.sourcery.ai) for detailed guides and information. - Keep in touch with the Sourcery team by following us on [X/Twitter](https://x.com/SourceryAI), [LinkedIn](https://www.linkedin.com/company/sourcery-ai/) or [GitHub](https://github.com/sourcery-ai).

[deepsource-io[bot]]

Here's the code health analysis summary for commits 8a9041f..eb8bb2e. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	✅ Success		View Check ↗
Java	✅ Success		View Check ↗
C#	✅ Success		View Check ↗
JavaScript	✅ Success		View Check ↗
Shell	✅ Success		View Check ↗
Kotlin	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[what-the-diff[bot]]

PR Summary

• GitHub Action Update for Node.js Setup The automated system involved in setting up Node.js, which is a crucial component of our technology that essentially lets our application function and communicate online, has been updated. Originally, we used version 3, but we've now shifted to version 4. This upgrade typically ensures a much smoother operation, and it may provide new features or better performance.

[github-actions[bot]]

🚨 Prettier check failed for the following files:

[warn] .github/workflows/package-v.yml
[warn] Code style issues found in the above file. Run Prettier with --write to fix.

To fix the issue, run the following command:

npx prettier --write .github/workflows/package-v.yml

[codiumai-pr-agent-free[bot]]

CI Failure Feedback 🧐

**Action:** Prettier Bot

**Failed stage:** [Prettier Bot](https://github.com/Andrewshin-7th-technology-student/build-CI/actions/runs/11469193781/job/31915928436) [❌]

**Failed test name:** ""

**Failure summary:** The action failed because the Prettier check detected code style issues in the file .github/workflows/package-v.yml. The file does not conform to the expected formatting standards.

Relevant error logs: ```yaml 1: ##[group]Operating System 2: Ubuntu ... 113: [command]/usr/local/bin/npm install --global prettier@3.x 114: added 1 package in 654ms 115: 1 package is looking for funding 116: run `npm fund` for details 117: [command]/usr/local/bin/prettier --check .github/workflows/package-v.yml 118: Checking formatting... 119: [warn] .github/workflows/package-v.yml 120: [warn] Code style issues found in the above file. Run Prettier with --write to fix. 121: ##[error] 122: Prettier check failed 😢 ```

---

✨ CI feedback usage guide:

---

The CI feedback tool (`/checks)` automatically triggers when a PR has a failed check. The tool analyzes the failed checks and provides several feedbacks: - Failed stage - Failed test name - Failure summary - Relevant error logs In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR: ``` /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}" ``` where `{repo_name}` is the name of the repository, `{run_number}` is the run number of the failed check, and `{job_number}` is the job number of the failed check. #### Configuration options - `enable_auto_checks_feedback` - if set to true, the tool will automatically provide feedback when a check is failed. Default is true. - `excluded_checks_list` - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list. - `enable_help_text` - if set to true, the tool will provide a help message with the feedback. Default is true. - `persistent_comment` - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true. - `final_update_message` - if `persistent_comment` is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true. See more information about the `checks` tool in the [docs](https://pr-agent-docs.codium.ai/tools/ci_feedback/).

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[renovate[bot]]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.