ci: Upgrade GitHub Action steps to github-script@v7

[mohanarpit]

Description

[!TIP]
Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content, marketing, and DevRel team).

Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

Fixes #Issue Number
or
Fixes Issue URL

[!WARNING]
If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation

/ok-to-test tags=""

:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication

Should the DevRel and Marketing teams inform users about this change?

• [ ] Yes
• [ ] No

[mohanarpit]

• #33556
• #33554 👈
• release

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @mohanarpit and the rest of your teammates on Graphite

[coderabbitai[bot]]

Walkthrough

Walkthrough

The recent updates across multiple GitHub Actions workflow files primarily involve upgrading the version of the actions/github-script from v6 to v7. This change is applied consistently across different workflows to ensure they benefit from the latest features, improvements, and bug fixes provided by the updated version of the action.

Changes

Files	Change Summary
.github/workflows/build-client-server.yml, .github/workflows/close-labeler.yml, .github/workflows/on-demand-build-docker-image-deploy-preview.yml, .github/workflows/pr-cypress.yml	Updated actions/github-script version from v6 to v7 in the respective workflow files.
.github/workflows/build-docker-image.yml, .github/workflows/client-build.yml, .github/workflows/github-release.yml, .github/workflows/rts-build.yml, .github/workflows/server-build.yml, .github/workflows/test-build-docker-image.yml	Updated actions/download-artifact or actions/upload-artifact from v3 to v4 in various workflows for downloading and uploading artifacts.
.github/workflows/ci-test-custom-script.yml, .github/workflows/ci-test-hosted.yml, .github/workflows/ci-test-limited.yml, .github/workflows/pr-cypress.yml	Upgraded actions/upload-artifact from v3 to v4 for artifact upload processes in different scenarios.

---

Recent Review Details

Configuration used: CodeRabbit UI Review profile: CHILL

Commits

Files that changed from the base of the PR and between e526099f142eb9bb50e9e1b00dab3d91a971e212 and 486857322cf267b37b492cbf74eaa73f6a705c6f.

Files selected for processing (12)

• .github/workflows/build-client-server.yml (4 hunks)
• .github/workflows/build-docker-image.yml (2 hunks)
• .github/workflows/ci-test-custom-script.yml (4 hunks)
• .github/workflows/ci-test-hosted.yml (1 hunks)
• .github/workflows/ci-test-limited.yml (4 hunks)
• .github/workflows/client-build.yml (1 hunks)
• .github/workflows/github-release.yml (5 hunks)
• .github/workflows/on-demand-build-docker-image-deploy-preview.yml (3 hunks)
• .github/workflows/pr-cypress.yml (2 hunks)
• .github/workflows/rts-build.yml (1 hunks)
• .github/workflows/server-build.yml (3 hunks)
• .github/workflows/test-build-docker-image.yml (6 hunks)

Files skipped from review due to trivial changes (8)

• .github/workflows/ci-test-custom-script.yml
• .github/workflows/ci-test-hosted.yml
• .github/workflows/ci-test-limited.yml
• .github/workflows/client-build.yml
• .github/workflows/github-release.yml
• .github/workflows/rts-build.yml
• .github/workflows/server-build.yml
• .github/workflows/test-build-docker-image.yml

Files skipped from review as they are similar to previous changes (3)

• .github/workflows/build-client-server.yml
• .github/workflows/on-demand-build-docker-image-deploy-preview.yml
• .github/workflows/pr-cypress.yml

Additional comments not posted (3)

.github/workflows/build-docker-image.yml (3)

41-41: Updated actions/download-artifact to v4 to leverage new features or improvements.

---

54-54: Updated actions/download-artifact to v4 to leverage new features or improvements.

---

61-61: Updated actions/download-artifact to v4 to leverage new features or improvements.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.