[WIP] Upgrade GitHub Actions versions

[adriangohjw]

Summary

Node.js 16 actions are deprecated and we want to update them to use the latest actions

Reference: Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@v3, actions/cache@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Changes

• Updated actions/setup-node@v3 to actions/setup-node@v4
• Updated actions/cache@v3 to actions/cache@v4
• Updated actions/upload-artifact@v3 to actions/upload-artifact@v4
  • Uploads are significantly faster, upwards of 90% improvement in worst case scenarios according to the documentation

Pull Request checklist

Remove this line after checking all the items here. If the item is not applicable to the PR, both check it out and wrap it by ~.

• ~[ ] Add/update test to cover these changes~
• ~[ ] Update documentation~
• [x] Update CHANGELOG file
  Add the CHANGELOG entry at the top of the file.

Other Information

Remove this paragraph and mention any other important and relevant information such as benchmarks.

---

This change is 

Summary by CodeRabbit

• Chores
  • Upgraded GitHub Actions setup and cache versions from v3 to v4 for enhanced performance and compatibility.
  • Updated workflows to utilize Node.js 20.0 versions.

[coderabbitai[bot]]

Walkthrough

The recent changes across multiple GitHub workflow files involve updating the versions of the setup-node, cache, and upload-artifact actions from v3 to v4. Additionally, in some workflows, filenames for uploaded test results and logs have been made dynamic to include GitHub context like run_id, job, and matrix.versions.

Changes

File Path	Change Summary
.github/workflows/examples.yml	Upgraded setup-node, cache, and upload-artifact actions from v3 to v4. Updated artifact naming convention.
.github/workflows/lint-js-and-ruby.yml	Upgraded setup-node and cache actions from v3 to v4.
.github/workflows/main.yml	Updated setup-node, cache, and upload-artifact actions from v3 to v4.
.github/workflows/package-js-tests.yml	Upgraded setup-node and cache actions from v3 to v4.
.github/workflows/rspec-package-specs.yml	Updated cache action from v3 to v4 and modified artifact naming convention.
CHANGELOG.md	Documented the upgrade of GitHub Actions to use Node.js 20.0 versions.

Poem

🐰✨

A rabbit hopped through code and file, Updating actions with a smile. From v3 to v4, the scripts do soar, With dynamic names and much, much more. GitHub workflows, sleek and bright, All thanks to changes made just right!

🌟🖥️

---

[!TIP]

Early access features: enabled

We are currently testing the following features in early access:

• OpenAI gpt-4o model for code reviews and chat: OpenAI claims that this model is better at understanding and generating code than the previous models. We seek your feedback over the next few weeks before making it generally available.

Note:

• You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.
• Please join our Discord Community to provide feedback and report issues.
• OSS projects are currently opted into early access features by default.

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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @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.

[justin808]

@adriangohjw can you investigate the CI failures?

[adriangohjw]

@justin808 alright will do, will look at it sometime this week 🫡

[justin808]

@adriangohjw any update?

[adriangohjw]

@justin808 sorry for the delay, fixed!

[justin808]

Thanks @adriangohjw