Skip to content

[CI] Update upmerge workflow to 2.2 -> 2.3#18730

Merged
TheMilek merged 1 commit intoSylius:2.3from
Rafikooo:ci/update-upmerge-branches
Jan 16, 2026
Merged

[CI] Update upmerge workflow to 2.2 -> 2.3#18730
TheMilek merged 1 commit intoSylius:2.3from
Rafikooo:ci/update-upmerge-branches

Conversation

@Rafikooo
Copy link
Copy Markdown
Contributor

@Rafikooo Rafikooo commented Jan 16, 2026 •
edited by coderabbitai bot
Loading

Removes old upmerge paths (1.14 -> 2.1, 2.1 -> 2.2) and sets up upmerge from 2.2 to 2.3. Also updates the workflow file link in PR body to point to the 2.3 branch.

Summary by CodeRabbit

  • Chores
    • Updated the upmerge workflow configuration to refine version merge scope and refresh reference links.

✏️ Tip: You can customize this high-level summary in your review settings.

@Rafikooo Rafikooo requested review from a team as code owners January 16, 2026 11:48
@probot-autolabeler probot-autolabeler bot added the Maintenance CI configurations, READMEs, releases, etc. label Jan 16, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Jan 16, 2026 •
edited
Loading

📝 Walkthrough

Walkthrough

Updates the upmerge GitHub Actions workflow to narrow the matrix from two base-target branch pairs to a single pair (2.2→2.3), and updates the corresponding reference link in the PR body to point to the 2.3 workflow file.

Changes

Cohort / File(s) Summary
Upmerge Workflow Configuration
\.github/workflows/upmerge_pr.yaml		 Matrix narrowed from two pairs (1.14→2.1, 2.1→2.2) to single pair (2.2→2.3); PR body link reference updated from 2.1 to 2.3 workflow path

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Suggested reviewers

  • GSadee
  • Wojdylak

Poem

🐰 Hop hop, the versions align,
Two-dot-two to three, how fine!
Old pathways fade with graceful care,
New workflows bloom in the GitHub air. 🌿

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title '[CI] Update upmerge workflow to 2.2 -> 2.3' directly and specifically describes the main change: updating the CI workflow matrix from old version pairs to 2.2→2.3.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 84b970e and c45bf26.

📒 Files selected for processing (1)
  • .github/workflows/upmerge_pr.yaml
🔇 Additional comments (3)
.github/workflows/upmerge_pr.yaml (3)

7-7: Manual trigger configuration looks good.
No issues with the workflow_dispatch setup.

23-25: Upmerge matrix scope update is clean.
The single 2.2 → 2.3 pair is consistent with the new objective.

57-59: PR body link update looks correct.
Pointing the reference to the 2.3 workflow path is appropriate.

✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jan 16, 2026 •
edited
Loading

❌ Preview Environment deleted from Bunnyshell

Available commands:

  • 🚀 /bns:deploy to redeploy the environment

@TheMilek TheMilek merged commit 697e998 into Sylius:2.3 Jan 16, 2026
29 of 36 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Feb 11, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@TheMilek TheMilek TheMilek approved these changes

Assignees

No one assigned

Labels

Maintenance CI configurations, READMEs, releases, etc.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Rafikooo @TheMilek