Skip to content

Chore: Update yarn to 4.9.1 and refactor CI#190

Merged
github-actions[bot] merged 1 commit intomainfrom
yarn-ver
Apr 19, 2025
Merged

Chore: Update yarn to 4.9.1 and refactor CI#190
github-actions[bot] merged 1 commit intomainfrom
yarn-ver

Conversation

@black7375
Copy link
Contributor

@black7375 black7375 commented Apr 19, 2025

Description

Related Issue

Summary by CodeRabbit

  • Chores
    • Updated Yarn to version 4.9.1 and adjusted related configuration settings.
    • Improved caching of Yarn files in the build process for faster and more reliable installs.
    • Enhanced GitHub workflow steps for rebase and fast-forward commands, improving reliability and accuracy.
    • Added dynamic branch selection in release workflows for better automation support.

Additional context

Checklist

@changeset-bot
Copy link

changeset-bot bot commented Apr 19, 2025

⚠️ No Changeset found

Latest commit: abaf21a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link

coderabbitai bot commented Apr 19, 2025

Warning

Rate limit exceeded

@black7375 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 6 minutes and 27 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 2d679a4 and abaf21a.

⛔ Files ignored due to path filters (2)
  • .yarn/releases/yarn-4.6.0.cjs is excluded by !**/.yarn/**
  • .yarn/releases/yarn-4.9.1.cjs is excluded by !**/.yarn/**
📒 Files selected for processing (6)
  • .github/actions/node-setup/action.yml (1 hunks)
  • .github/workflows/ci.yml (0 hunks)
  • .github/workflows/fast-forward.yml (3 hunks)
  • .github/workflows/rebase.yml (1 hunks)
  • .yarnrc.yml (1 hunks)
  • package.json (1 hunks)

Walkthrough

This set of changes updates several configuration files related to Yarn and GitHub Actions workflows. The Yarn version is upgraded from 4.6.0 to 4.9.1, and cache paths are extended to improve caching efficiency. The .yarnrc.yml file is updated to adjust cache and store directories and to reflect the new Yarn version. GitHub Actions workflows for fast-forwarding and rebasing are refactored to use step outputs instead of environment variables, and a new step is introduced to dynamically fetch the pull request branch for releases.

Changes

File(s) Change Summary
.github/actions/node-setup/action.yml Expanded Yarn cache paths; added yarn config set winLinkType symlinks before install.
.github/workflows/fast-forward.yml Outputs now use $GITHUB_OUTPUT; conditionals updated to use step outputs; added step to fetch PR branch and updated checkout logic.
.github/workflows/rebase.yml Outputs now use $GITHUB_OUTPUT; conditionals updated to use step outputs.
.yarnrc.yml, package.json Updated Yarn version from 4.6.0 to 4.9.1; changed Yarn cache/store paths; added pnpmStoreFolder config.

Sequence Diagram(s)

sequenceDiagram
    participant GitHub Actions
    participant Node Setup Action
    participant Yarn

    GitHub Actions->>Node Setup Action: Start setup
    Node Setup Action->>Yarn: Set winLinkType symlinks
    Node Setup Action->>Yarn: Install dependencies
    Node Setup Action->>Yarn: Cache .yarn/cache, .yarn/unplugged, etc.
Loading
sequenceDiagram
    participant GitHub Actions
    participant PR Branch Fetch Step
    participant Checkout Step

    GitHub Actions->>PR Branch Fetch Step: Get PR number from event context
    PR Branch Fetch Step->>GitHub API: Fetch PR branch name
    PR Branch Fetch Step-->>GitHub Actions: Output branch name
    GitHub Actions->>Checkout Step: Checkout using fetched branch name
Loading

Possibly related PRs

Poem

Hopping through configs with nimble delight,
Yarn’s cache grows stronger, the workflows take flight.
Fast-forward and rebase now output with care,
New branches are fetched from digital air.
With version 4.9.1, our threads are spun tight—
The code garden’s blooming, oh what a sight!
🐇✨


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

@black7375 black7375 added the config/build Config or Build system label Apr 19, 2025
@github-actions
Copy link
Contributor

Triggered from #190 by @​black7375.

Checking if we can fast forward main (93841d4) to yarn-ver (5ade098).

Target branch (main):

commit 93841d4d6fb315623964005a1ec2c51bd4a54fba (HEAD -> main, origin/main)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:12:41 2025 +0900

    Chore: Rebase Action

Pull request (yarn-ver):

commit 5ade09804e97f83ac34526448d5200b8db37ceee (pull_request/yarn-ver)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:22:23 2025 +0900

    Chore: Update yarn to 4.9.1 and refactor CI

It is possible to fast forward main (93841d4) to yarn-ver (5ade098). If you have write access to the target repository, you can add a comment with /fast-forward to fast forward main to yarn-ver.

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.

Actionable comments posted: 0

🔭 Outside diff range comments (1)
.github/workflows/rebase.yml (1)

58-62: ⚠️ Potential issue

Undefined MAIN_HEAD variable breaks rebase check
The script compares the current HEAD to $MAIN_HEAD, but MAIN_HEAD is never initialized. This renders the “already up to date” logic ineffective. Capture the base-branch HEAD immediately after the checkout. For example:

-          PR_HEAD=$(git rev-parse HEAD)
+          MAIN_HEAD=$(git rev-parse HEAD)                # capture base branch HEAD
+          PR_HEAD=$(git rev-parse HEAD)

Ensure MAIN_HEAD is set right after the initial actions/checkout step.

🧹 Nitpick comments (3)
.github/actions/node-setup/action.yml (1)

25-30: Expand Yarn cache paths for optimal CI performance
Adding .yarn/unplugged, .yarn/build-state.yml, and .yarn/install-state.gz will reduce install times by preserving more of Yarn’s state. Consider also caching .yarn/patches and .yarn/plugins to further speed up your workflow.

.github/workflows/rebase.yml (1)

31-43: Reference steps.check_comment.outputs.MATCH in conditional steps
All the conditional steps now correctly use the step output syntax (steps.check_comment.outputs.MATCH). To DRY up the workflow, you could lift this to a job-level if so you don’t repeat the same condition on each step.

.github/workflows/fast-forward.yml (1)

33-33: Guard steps with the MATCH output
The if: steps.check_comment.outputs.MATCH == 'true' clauses ensure the fast-forward and branch-check steps only run when /fast-forward is detected. As an enhancement, consider moving this to a job-level if to reduce duplication.

Also applies to: 45-45

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 93841d4 and 5ade098.

⛔ Files ignored due to path filters (2)
  • .yarn/releases/yarn-4.6.0.cjs is excluded by !**/.yarn/**
  • .yarn/releases/yarn-4.9.1.cjs is excluded by !**/.yarn/**
📒 Files selected for processing (5)
  • .github/actions/node-setup/action.yml (1 hunks)
  • .github/workflows/fast-forward.yml (3 hunks)
  • .github/workflows/rebase.yml (1 hunks)
  • .yarnrc.yml (1 hunks)
  • package.json (1 hunks)
🔇 Additional comments (6)
package.json (1)

5-5: Align Yarn version with project configuration
The packageManager field is correctly updated to yarn@4.9.1, matching the version in .yarnrc.yml. This ensures consistency across local and CI environments.

.yarnrc.yml (1)

19-22:

Details

✅ Verification successful

Configure PNPM store and bump Yarn path
The new pnpmStoreFolder directive at line 19 guides the PNPM store location, and the updated yarnPath at line 21 correctly points to the Yarn v4.9.1 release. Ensure that .yarn/releases/yarn-4.9.1.cjs is committed to the repo.

Run this script to verify the Yarn release file is present:


🏁 Script executed:

#!/bin/bash
if [ ! -f .yarn/releases/yarn-4.9.1.cjs ]; then
  echo "Error: .yarn/releases/yarn-4.9.1.cjs not found"
  exit 1
fi
echo "✅ Yarn release file exists."

Length of output: 111


Configure PNPM store and bump Yarn path

  • pnpmStoreFolder is correctly set to .cache/.store.
  • yarnPath points to .yarn/releases/yarn-4.9.1.cjs, and the file exists in the repo.

All changes look good—approving.

.github/actions/node-setup/action.yml (1)

36-36: Enable Windows symlink support for Yarn
The yarn config set winLinkType symlinks command ensures proper symlink behavior on Windows runners. Leaving it unguarded is fine since it’s a no-op on non-Windows hosts.

.github/workflows/rebase.yml (1)

25-28: Switch to using $GITHUB_OUTPUT for step outputs
Updating to echo "MATCH=…" >> $GITHUB_OUTPUT aligns with the deprecation notice for save-state/set-output and correctly sets steps.check_comment.outputs.MATCH.

.github/workflows/fast-forward.yml (2)

27-30: Use $GITHUB_OUTPUT to export the match result
Switching from the deprecated $GITHUB_ENV to $GITHUB_OUTPUT aligns with the latest Actions recommendations and correctly publishes MATCH as a step output.


116-125: Dynamically fetch and checkout the PR branch for release
Retrieving the PR branch via the GitHub API and using ref: ${{ steps.get_pr_branch.outputs.branch }} now correctly targets the contributor’s branch instead of defaulting to main.

Also applies to: 130-131

@github-actions
Copy link
Contributor

Triggered from #190 (comment) by @​coderabbitai[bot].

Trying to fast forward main (93841d4) to yarn-ver (5ade098).

Target branch (main):

commit 93841d4d6fb315623964005a1ec2c51bd4a54fba (HEAD -> main, origin/main)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:12:41 2025 +0900

    Chore: Rebase Action

Pull request (yarn-ver):

commit 5ade09804e97f83ac34526448d5200b8db37ceee (pull_request/yarn-ver)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:22:23 2025 +0900

    Chore: Update yarn to 4.9.1 and refactor CI

curl: (3) bad range in URL position 74:
https://api.github.com/repos/mincho-js/mincho/collaborators/coderabbitai[bot]/permission
^

@github-actions
Copy link
Contributor

Triggered from #190 by @​black7375.

Checking if we can fast forward main (93841d4) to yarn-ver (e81d9c8).

Target branch (main):

commit 93841d4d6fb315623964005a1ec2c51bd4a54fba (HEAD -> main, origin/main)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:12:41 2025 +0900

    Chore: Rebase Action

Pull request (yarn-ver):

commit e81d9c8423a75c52fadc8be19c05df611686d9e4 (pull_request/yarn-ver)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:28:22 2025 +0900

    Chore: Update yarn to 4.9.1 and refactor CI

It is possible to fast forward main (93841d4) to yarn-ver (e81d9c8). If you have write access to the target repository, you can add a comment with /fast-forward to fast forward main to yarn-ver.

@github-actions
Copy link
Contributor

Triggered from #190 (comment) by @​coderabbitai[bot].

Trying to fast forward main (93841d4) to yarn-ver (e81d9c8).

Target branch (main):

commit 93841d4d6fb315623964005a1ec2c51bd4a54fba (HEAD -> main, origin/main)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:12:41 2025 +0900

    Chore: Rebase Action

Pull request (yarn-ver):

commit e81d9c8423a75c52fadc8be19c05df611686d9e4 (pull_request/yarn-ver)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:28:22 2025 +0900

    Chore: Update yarn to 4.9.1 and refactor CI

curl: (3) bad range in URL position 74:
https://api.github.com/repos/mincho-js/mincho/collaborators/coderabbitai[bot]/permission
^

1 similar comment
@github-actions
Copy link
Contributor

Triggered from #190 (comment) by @​coderabbitai[bot].

Trying to fast forward main (93841d4) to yarn-ver (e81d9c8).

Target branch (main):

commit 93841d4d6fb315623964005a1ec2c51bd4a54fba (HEAD -> main, origin/main)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:12:41 2025 +0900

    Chore: Rebase Action

Pull request (yarn-ver):

commit e81d9c8423a75c52fadc8be19c05df611686d9e4 (pull_request/yarn-ver)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:28:22 2025 +0900

    Chore: Update yarn to 4.9.1 and refactor CI

curl: (3) bad range in URL position 74:
https://api.github.com/repos/mincho-js/mincho/collaborators/coderabbitai[bot]/permission
^

@github-actions
Copy link
Contributor

Triggered from #190 by @​black7375.

Checking if we can fast forward main (93841d4) to yarn-ver (2d679a4).

Target branch (main):

commit 93841d4d6fb315623964005a1ec2c51bd4a54fba (HEAD -> main, origin/main)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:12:41 2025 +0900

    Chore: Rebase Action

Pull request (yarn-ver):

commit 2d679a4c7bf11c0c1ce53ed9ad30397a3788c2b0 (pull_request/yarn-ver)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:43:05 2025 +0900

    Chore: Update yarn to 4.9.1 and refactor CI

It is possible to fast forward main (93841d4) to yarn-ver (2d679a4). If you have write access to the target repository, you can add a comment with /fast-forward to fast forward main to yarn-ver.

@github-actions
Copy link
Contributor

Triggered from #190 (comment) by @​coderabbitai[bot].

Trying to fast forward main (93841d4) to yarn-ver (2d679a4).

Target branch (main):

commit 93841d4d6fb315623964005a1ec2c51bd4a54fba (HEAD -> main, origin/main)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:12:41 2025 +0900

    Chore: Rebase Action

Pull request (yarn-ver):

commit 2d679a4c7bf11c0c1ce53ed9ad30397a3788c2b0 (pull_request/yarn-ver)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:43:05 2025 +0900

    Chore: Update yarn to 4.9.1 and refactor CI

curl: (3) bad range in URL position 74:
https://api.github.com/repos/mincho-js/mincho/collaborators/coderabbitai[bot]/permission
^

@github-actions
Copy link
Contributor

Triggered from #190 by @​black7375.

Checking if we can fast forward main (93841d4) to yarn-ver (abaf21a).

Target branch (main):

commit 93841d4d6fb315623964005a1ec2c51bd4a54fba (HEAD -> main, origin/main)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:12:41 2025 +0900

    Chore: Rebase Action

Pull request (yarn-ver):

commit abaf21a820070455e136ebcf3a48883e09ad2449 (pull_request/yarn-ver)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:46:37 2025 +0900

    Chore: Update yarn to 4.9.1 and refactor CI

It is possible to fast forward main (93841d4) to yarn-ver (abaf21a). If you have write access to the target repository, you can add a comment with /fast-forward to fast forward main to yarn-ver.

@black7375
Copy link
Contributor Author

/fast-forward

@github-actions
Copy link
Contributor

Triggered from #190 (comment) by @​black7375.

Trying to fast forward main (93841d4) to yarn-ver (abaf21a).

Target branch (main):

commit 93841d4d6fb315623964005a1ec2c51bd4a54fba (HEAD -> main, origin/main)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:12:41 2025 +0900

    Chore: Rebase Action

Pull request (yarn-ver):

commit abaf21a820070455e136ebcf3a48883e09ad2449 (pull_request/yarn-ver)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:46:37 2025 +0900

    Chore: Update yarn to 4.9.1 and refactor CI

Fast forwarding main (93841d4) to yarn-ver (abaf21a).

$ git push origin abaf21a820070455e136ebcf3a48883e09ad2449:main
To https://github.com/mincho-js/mincho.git
   93841d4..abaf21a  abaf21a820070455e136ebcf3a48883e09ad2449 -> main

@github-actions github-actions bot merged commit abaf21a into main Apr 19, 2025
9 checks passed
@github-actions github-actions bot deleted the yarn-ver branch April 19, 2025 22:49
@coderabbitai coderabbitai bot mentioned this pull request Jan 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

config/build Config or Build system

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant