Fix condition for package check in build workflow

[hupling]

Pull Request

Changes

• ...
• ...

Reference

Issue: #XXX

Checklist

Note: If some checklist items are not relevant for your PR, just remove them.

General

• I have read the Contribution Guidelines (TBD)
• Met all acceptance criteria of the issue
• Added meaningful PR title and list of changes in the description
• Opened documentation issue in refarch repository (if applicable)
• Opened follow-up issue in refarch repository (if applicable)

Code

• Wrote code and comments in English
• Added unit tests
• Removed waste on branch (e.g. console.log), see code quality tooling

Frontend / WebComponent

• Added component tests (if component was changed)
• Considered and tested accessibility (if UI change was made)
• Checked / Updated Node.js engine requirements in package.json (if dependencies were changed)
• Tested changes using API gateway

Backend / EAI

• Added integration tests
• Updated database migration scripts (if changes to model were made)
• Added Swagger API annotations (if changes to API was made)
• Checked Spring Boot version matching Camel version in pom.xml (if Camel version was bumped)

Development Stack

• Checked functionality of Docker stack (if Docker stack was modified or images were changed)

Screenshots (if UI was changed)

[coderabbitai]

Warning

Review limit reached

@hupling, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 46 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 6c310396-5e18-4fed-a382-43ef859de813

📥 Commits

Reviewing files that changed from the base of the PR and between e59fac0 and 68bfa19.

📒 Files selected for processing (1)

• .github/workflows/build.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch test-con1

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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