Walkthrough

The upmerge workflow’s matrix was reduced to a single branch pair: base 2.1 to target 2.2. All other workflow logic, triggers, and PR creation steps remain unchanged.

Changes

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• [CI] Update branches for full builds + refactor and upmerge actions #17887 — Also updates .github/workflows/upmerge_pr.yaml, focusing on branch references/URL in the PR body.
• [UPMERGE] 2.0 -> 2.1 #17904 — Adjusts the same upmerge workflow’s matrix entries for different base/target pairs.

Suggested labels

CI

Suggested reviewers

• TheMilek

Poem

I hopped through branches, light and spry,
From 2.1 to 2.2 I fly—
A single path, a tidy queue,
No extra burrows to tunnel through.
Thump-thump! says CI, crisp and new. 🐇✨

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

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.

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

❗ Preview Environment deployment failed on Bunnyshell

See: Environment Details | Pipeline Logs

Check https://github.com/Sylius/Sylius/actions/runs/17987519520 for details.

Available commands:

• 🚀 /bns:deploy to redeploy the environment
• ❌ /bns:delete to remove the environment