Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Ruby and Node #1873

Merged
merged 1 commit into from
Jan 29, 2025
Merged

Update Ruby and Node #1873

merged 1 commit into from
Jan 29, 2025

Conversation

tagliala
Copy link
Member

@tagliala tagliala commented Jan 29, 2025

Summary by CodeRabbit

  • Chores
    • Updated Ruby version from 3.3.6 to 3.4.1 across project configuration files
    • Updated Node.js version from 20 to 22 in CI workflows and package requirements
    • Modified Dockerfile and version specifications to align with new runtime versions

Copy link

coderabbitai bot commented Jan 29, 2025

Warning

Rate limit exceeded

@tagliala has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 8 minutes and 55 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 9fb66ed and dcec1c2.

⛔ Files ignored due to path filters (1)
  • Gemfile.lock is excluded by !**/*.lock
📒 Files selected for processing (6)
  • .github/workflows/ci.yml (1 hunks)
  • .github/workflows/lint.yml (4 hunks)
  • .rubocop.yml (1 hunks)
  • Gemfile (1 hunks)
  • docker/icare/Dockerfile (1 hunks)
  • package.json (1 hunks)

Walkthrough

This pull request focuses on upgrading the Ruby and Node.js versions across multiple configuration files and project settings. The changes systematically update the Ruby version from 3.3.6 to 3.4.1 and the Node.js version from 20 to 22 in CI workflows, Dockerfile, Gemfile, and package.json. These modifications ensure consistent version requirements across the project's development and deployment environments.

Changes

File Change Summary
.github/workflows/ci.yml Updated Ruby version to 3.4.1 and Node.js version to 22
.github/workflows/lint.yml Updated Ruby version to 3.4.1 and Node.js version to 22 in linting jobs
Gemfile Updated Ruby version requirement to 3.4.1
docker/icare/Dockerfile Updated RUBY_VERSION argument to 3.4.1
package.json Updated Node.js version requirement to >= 22.0

Possibly related PRs

Poem

🐰 Hop, hop, version upgrade dance!
Ruby and Node.js take a new stance
From 3.3 to 3.4, from 20 to 22
Our code leaps forward with magical glee
Configuration files sing their version song! 🚀


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
🪧 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.
    • 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 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 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 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. (Beta)
  • @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.

@coveralls
Copy link

coveralls commented Jan 29, 2025

Coverage Status

coverage: 96.914%. remained the same
when pulling dcec1c2 on chore/ruby-node
into c5d232c on main.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Inline review comments failed to post. This is likely due to GitHub's limits when posting large numbers of comments.

Actionable comments posted: 3

🛑 Comments failed to post (3)
docker/icare/Dockerfile (1)

4-4: ⚠️ Potential issue

Update Node version in Dockerfile to match other configurations

While the Ruby version has been updated to 3.4.1, the Node version (20.10.0) in the Dockerfile doesn't match the version 22 specified in other configuration files.

Apply this diff to maintain consistency:

-ARG NODE_VERSION=20.10.0
+ARG NODE_VERSION=22.0.0

Also applies to: 27-27

package.json (1)

6-6: 💡 Codebase verification

Consider using Node 20 LTS instead of Node 22

Node 22 is currently in development and not yet released for production use. While your dependencies don't explicitly prohibit Node 22, using the current LTS version (Node 20) would be more reliable for production environments.

🔗 Analysis chain

Verify package compatibility with Node 22

Node 22 is a very recent release. Let's verify compatibility with key dependencies.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check package compatibility with Node 22
for pkg in @babel/core shakapacker webpack; do
  echo "Checking $pkg..."
  curl -s "https://registry.npmjs.org/$pkg" | jq -r '.versions | keys[]' | sort -V | tail -n 1
  curl -s "https://registry.npmjs.org/$pkg" | jq -r '.versions | to_entries[] | select(.value.engines?.node != null) | .value.engines.node' | tail -n 1
done

Length of output: 1112

.github/workflows/lint.yml (1)

33-33: ⚠️ Potential issue

Update Ruby version in slim-lint job to match other configurations

The Ruby version has been updated to 3.4.1 in the rubocop job, but the slim-lint job still uses 3.3.6. This inconsistency should be fixed.

Apply this diff to maintain consistency:

-        ruby-version: '3.3.6'
+        ruby-version: '3.4.1'

Also applies to: 52-52

@tagliala tagliala merged commit 46b4ee9 into main Jan 29, 2025
6 checks passed
@tagliala tagliala deleted the chore/ruby-node branch January 29, 2025 09:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants