[coodos]

Description of change

Issue Number

Type of change

• Chore (refactoring, build scripts or anything else that isn't user-facing)

How the change has been tested

Change checklist

• I have ensured that the CI Checks pass locally
• I have removed any unnecessary logic
• My code is well documented
• I have signed my commits
• My code follows the pattern of the application
• I have self reviewed my code

Summary by CodeRabbit

• Chores
  • Updated Next.js framework dependency to version 15.5.7 across all platform packages.

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

[coderabbitai]

Warning

Rate limit exceeded

@coodos has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 19 minutes and 56 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 2020a2a and 0ebf9c9.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (3)

• platforms/blabsy/package.json (3 hunks)
• platforms/eVoting/package.json (2 hunks)
• platforms/group-charter-manager/package.json (1 hunks)

Walkthrough

Four package.json files across different platforms are updated to bump the Next.js dependency from version 15.4.2 to 15.5.7. No other dependencies are modified, and no functional code changes are introduced.

Changes

Cohort / File(s)	Summary
Next.js dependency version updates platforms/blabsy/package.json, platforms/eVoting/package.json, platforms/evoting-api/package.json, platforms/group-charter-manager/package.json	Next.js dependency bumped from 15.4.2 to 15.5.7 across all four platform package.json files.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Verify Next.js 15.5.7 is a stable release without breaking changes for the codebase
• Confirm all four package.json files are updated consistently with the same version

Poem

🐰 Four platforms, one update so small,
Next.js nudges upward through the hall,
15.5.7 arrives with grace,
No breaking changes to embrace,
Hop along to a smoother place! 🚀

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title mentions 'bump depenencies' which aligns with the changes (Next.js version updates across multiple package.json files), but contains a spelling error ('depenencies' instead of 'dependencies').
Description check	✅ Passed	The description follows the required template structure with all key sections present, though 'How the change has been tested' is left blank and no issue number is provided.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (1)

platforms/evoting-api/package.json (1)

48-48: Add trailing newline at end of file.

The file currently ends without a newline character (noted in the summary). Most projects and linters expect files to end with a newline for consistency.

Add a newline after the closing brace on line 48.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6db924a and 2020a2a.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (4)

• platforms/blabsy/package.json (2 hunks)
• platforms/eVoting/package.json (1 hunks)
• platforms/evoting-api/package.json (2 hunks)
• platforms/group-charter-manager/package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build

🔇 Additional comments (2)

platforms/evoting-api/package.json (1)

24-24: Verify Next.js 15.5.7 compatibility with backend API dependencies.

The upgrade to Next.js 15.5.7 looks correct. However, since this is an API package using Next.js in a backend context, ensure that no code changes are needed. The Next.js 15.5 release does not indicate breaking changes from 15.4.2, but verify the changelog if any middleware, API routes, or configuration relies on version-specific behavior.

platforms/group-charter-manager/package.json (1)

2-70: Verify the extensive formatting reflow is intentional.

Nearly all lines in this file are marked as changed (line 2–70), suggesting comprehensive reformatting beyond the Next.js version bump. The PR description indicates this is a chore for dependency bumping, so verify whether this reformat was:

• Intentional (auto-applied by a formatting tool during the dependency update), or
• Unintended (accidental reformatting that should be separated into a distinct commit).

If intentional, consider separating formatting changes from dependency changes in a future PR for clearer commit history.