build: update setup-node to v4

[eeemmmmmm]

Updated actions/setup-node to v4 for better compatibility with the latest runner environments. Workflows only updated—no functional changes. Release notes: https://github.com/actions/setup-node/releases/tag/v4.0.0

Summary by CodeRabbit

• Chores
  • Upgraded Node.js setup in GitHub Actions workflows to use the latest version for improved reliability and support. No changes to user-facing features or functionality.

[coderabbitai]

Walkthrough

The GitHub Actions workflows have been updated to use actions/setup-node@v4 instead of v3 for Node.js environment setup. This change was applied across workflows related to publishing, pull request automation, and image synchronization. No other workflow logic, steps, or configurations were altered.

Changes

Files/Paths	Change Summary
.github/workflows/npm_pr_initia_registry.yml	Updated actions/setup-node from v3 to v4.
.github/workflows/npm_pr_types.yml	Updated actions/setup-node from v3 to v4.
.github/workflows/npm_publish_initia_registry.yml	Updated actions/setup-node from v3 to v4.
.github/workflows/npm_publish_types.yml	Updated actions/setup-node from v3 to v4.
.github/workflows/sync_images.yml	Updated actions/setup-node from v3 to v4.

Poem

Hopping through workflows, what do I see?
A shiny new node, now version four, yippee!
Actions are nimble, the steps are all neat,
With v4 in the burrow, our builds can’t be beat.
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e5f13b8 and 7f9144f.

📒 Files selected for processing (5)

• .github/workflows/npm_pr_initia_registry.yml (1 hunks)
• .github/workflows/npm_pr_types.yml (1 hunks)
• .github/workflows/npm_publish_initia_registry.yml (1 hunks)
• .github/workflows/npm_publish_types.yml (1 hunks)
• .github/workflows/sync_images.yml (1 hunks)

🔇 Additional comments (5)

.github/workflows/npm_publish_types.yml (1)

15-15: Update Node.js setup action to v4

Upgraded actions/setup-node from v3 to v4; configuration (node-version, registry-url) remains correct.

.github/workflows/npm_pr_initia_registry.yml (1)

19-19: Upgrade Node.js setup action to v4

Consistent update to use actions/setup-node@v4; Node version remains at 20.x.

.github/workflows/sync_images.yml (1)

21-21: Upgrade Node.js setup action to v4

Using the latest setup-node action for improved compatibility.

.github/workflows/npm_publish_initia_registry.yml (1)

15-15: Bump setup-node action to v4

Aligned this workflow with others by upgrading actions/setup-node to v4; Node version unchanged.

.github/workflows/npm_pr_types.yml (1)

19-19: Use actions/setup-node@v4

Upgraded from v3 to v4; no further changes needed.

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.