Update github-ci actions to latest commit#983
Conversation
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdds a new GitHub Actions workflow for release preparation that reuses an external workflow with dispatch inputs and secrets. Updates an existing release workflow's reusable workflow reference commit. Upgrades Maven parent POM from version 22 to 26. Applies formatting adjustments and updates copyright year in a service file. Changes
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the 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. Review rate limit: 0/1 reviews remaining, refill in 40 minutes and 9 seconds.Comment |
Signed-off-by: Radouane Khouadri <redouane.khouadri_externe@rte-france.com>
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@pom.xml`:
- Line 16: The parent POM references a non-existent version (26) of
com.powsybl:powsybl-parent-ws which breaks dependency resolution; update the
<version> element under the parent declaration in pom.xml (the
com.powsybl:powsybl-parent-ws parent block) to a valid released version such as
22 (or 23/25), save the change, and re-run the Maven build to confirm resolution
succeeds.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 823ea428-7830-4d0c-ba91-23cef7a5c565
📒 Files selected for processing (4)
.github/workflows/prepare-release.yml.github/workflows/release.ymlpom.xmlsrc/main/java/org/gridsuite/study/server/service/SupervisionService.java
| <groupId>com.powsybl</groupId> | ||
| <artifactId>powsybl-parent-ws</artifactId> | ||
| <version>22</version> | ||
| <version>26</version> |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
What are the breaking changes (if any) between com.powsybl:powsybl-parent-ws version 22 and version 26, and which managed dependency/plugin versions changed?
💡 Result:
No version 26 of com.powsybl:powsybl-parent-ws exists on Maven Central as of 2026-04-29. The latest version is 22, released 2025-03-19. The parent powsybl-parent has releases up to v25 (2025-12-04), but powsybl-parent-ws POMs only go up to v22 in available data. No breaking changes or dependency/plugin version changes can be identified between non-existent v26 and v22. Minor patch releases like v22 to v22.1 and v22 to v23 mainly involve version bumps (e.g., checkstyle 3.1.3 to 3.1.4, checkstyle.version 11.0.1 added, Maven deploy plugin adjustments, migration to Central Portal from OSSRH) and checkstyle.xml header updates, with no explicit breaking changes documented.
Citations:
- 1: https://central.sonatype.com/artifact/com.powsybl/powsybl-parent-ws
- 2: https://github.com/powsybl/powsybl-parent
- 3: powsybl/powsybl-parent@v22...v23
- 4: powsybl/powsybl-parent@v22.1...v22.2
- 5: powsybl/powsybl-parent@v22...v22.1
🌐 Web query:
Is com.powsybl:powsybl-parent-ws version 26 the current recommended version for GridSuite services, and are there migration notes for projects upgrading from 22?
💡 Result:
No, com.powsybl:powsybl-parent-ws version 26 does not exist and is not the current recommended version for GridSuite services. The latest released version is 22 (released 2025-03-19), with indications of v23 and v25 in GitHub repositories. GridSuite services use powsybl-ws-dependencies (latest v2.22.0, parent powsybl v22) and gridsuite-dependencies (v40.0.0, parent powsybl v22). PowSyBl parent latest release is v25. No specific migration notes from v22 were found; upgrades typically involve pull requests updating dependencies like powsybl-dependencies (e.g., to 2026.0.0 or v2025.x), adjusting code for API changes (e.g., DanglingLine to BoundaryLine), and removing redundant logic handled in newer PowSyBl core versions.
Citations:
- 1: https://central.sonatype.com/artifact/com.powsybl/powsybl-parent-ws
- 2: https://github.com/powsybl/powsybl-parent
- 3: https://central.sonatype.com/artifact/com.powsybl/powsybl-ws-dependencies
- 4: https://central.sonatype.com/artifact/org.gridsuite/gridsuite-dependencies
- 5: https://github.com/gridsuite/network-modification/network/dependencies
- 6: https://mvnrepository.com/artifact/com.powsybl/powsybl-parent-ws/versions
- 7: https://central.sonatype.com/artifact/com.powsybl/powsybl-ws-commons
- 8: https://github.com/powsybl/powsybl-dependencies
- 9: powsybl/powsybl-parent@v22...v23
- 10: Upgrade for powsybl-dependencies 2026.0.0 network-modification#173
- 11: powsybl-dependencies v2025.3.0 sensitivity-analysis-server#150
- 12: https://github.com/powsybl/powsybl-parent/
- 13: https://github.com/gridsuite/documentation
Parent POM references non-existent version 26 — build will fail.
Version 26 of com.powsybl:powsybl-parent-ws does not exist. The latest released version is 22. This version reference will cause a Maven build failure during dependency resolution. Update to an available version (22, 23, or 25).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@pom.xml` at line 16, The parent POM references a non-existent version (26) of
com.powsybl:powsybl-parent-ws which breaks dependency resolution; update the
<version> element under the parent declaration in pom.xml (the
com.powsybl:powsybl-parent-ws parent block) to a valid released version such as
22 (or 23/25), save the change, and re-run the Maven build to confirm resolution
succeeds.
|
2 participants
This PR updates GitHub Actions workflows to reference the latest commit of powsybl/github-ci.