Upgrade parent to v26.1#999
Conversation
Signed-off-by: BOUHOURS Antoine <antoine.bouhours@rte-france.com>
📝 WalkthroughWalkthroughThe Maven ChangesParent POM Configuration
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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. Comment |
![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 current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@pom.xml`:
- Line 16: Update and validate the parent POM change to
com.powsybl:powsybl-parent-ws:26.1 by confirming the artifact is resolvable in
your build environment, then assess impact of the bumped properties
maven.spring-boot.version (3.4.9→3.5.11) and liquibase.version (4.29.2→4.31.1)
by reviewing the parent POM for breaking changes and property overrides, running
the full test suite (unit, integration, and DB migration tests) and any
Liquibase changelog validations, and addressing incompatibilities (Spring Boot
or Liquibase API changes, dependency version conflicts, or migration behavior)
in the code or dependency management (e.g., overriding properties or updating
modules) until tests pass.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| <groupId>com.powsybl</groupId> | ||
| <artifactId>powsybl-parent-ws</artifactId> | ||
| <version>26</version> | ||
| <version>26.1</version> |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
powsybl-parent-ws version 26.1 Maven release notes
💡 Result:
I couldn’t find any “powsybl-parent-ws 26.1” Maven release notes. What I found instead: 1) Maven Central / Sonatype shows powsybl-parent-ws versions only up to 22 (and older); there is no 26.1 version listed for the powsybl-parent-ws artifact. [1] 2) The powsybl GitHub repository’s “powsybl-parent-ws” is described as a web-services parent pom (via Spring + Jib), but release-notes content for a 26.1 tag/version isn’t present in the sources I located. [2] If you meant a different artifact (for example a different “parent” or a module under powsybl-ws-*), tell me the exact Maven coordinates (groupId/artifactId/version) and I can re-run the search for the correct 26.1 release notes.
Citations:
- 1: https://central.sonatype.com/artifact/com.powsybl/powsybl-parent-ws
- 2: https://github.com/powsybl/powsybl-parent/
🏁 Script executed:
#!/bin/bash
# Description: Verify that the parent POM version exists and can be resolved
# Attempt to download the parent POM to verify it exists
curl -s -f -I "https://repo1.maven.org/maven2/com/powsybl/powsybl-parent-ws/26.1/powsybl-parent-ws-26.1.pom" > /dev/null 2>&1
if [ $? -eq 0 ]; then
echo "✓ Parent POM version 26.1 exists in Maven Central"
# Fetch and display basic info about the POM
curl -s "https://repo1.maven.org/maven2/com/powsybl/powsybl-parent-ws/26.1/powsybl-parent-ws-26.1.pom" | head -n 30
else
echo "✗ Parent POM version 26.1 not found in Maven Central"
echo "Checking available versions..."
curl -s "https://repo1.maven.org/maven2/com/powsybl/powsybl-parent-ws/maven-metadata.xml" | grep -A 100 "<versions>"
fiRepository: gridsuite/study-server
Length of output: 1239
🏁 Script executed:
#!/bin/bash
set -euo pipefail
BASE="https://repo1.maven.org/maven2/com/powsybl/powsybl-parent-ws"
echo "== Maven metadata =="
curl -s "$BASE/maven-metadata.xml" | sed -n '1,160p'
echo "== Try fetch 26 (parent version in project) =="
for v in 26 26.1; do
url="$BASE/$v/powsybl-parent-ws-$v.pom"
echo "--- HEAD $url"
if curl -s -f -I "$url" >/dev/null; then
echo "OK $v"
else
echo "MISSING $v"
fi
done
echo "== Extract key version properties from 26 and 26.1 POMs =="
for v in 26 26.1; do
url="$BASE/$v/powsybl-parent-ws-$v.pom"
echo "## $v"
curl -s "$url" | rg -n --no-heading -S \
"(spring-boot\\.version|jib\\.version|maven\\.[a-zA-Z0-9_.-]*\\.version|pluginManagement|dependencyManagement|<properties>|<build>|<plugin>)" \
| head -n 200
done
echo "== Compare: show differing lines (small excerpt) =="
# Use unified diff limited to first ~200 lines to avoid noise.
tmp26="/tmp/powsybl-parent-ws-26.pom"
tmp261="/tmp/powsybl-parent-ws-26.1.pom"
curl -s "$BASE/26/powsybl-parent-ws-26.pom" > "$tmp26" || true
curl -s "$BASE/26.1/powsybl-parent-ws-26.1.pom" > "$tmp261" || true
if [ -s "$tmp26" ] && [ -s "$tmp261" ]; then
diff -u "$tmp26" "$tmp261" | head -n 220
else
echo "Cannot diff: one of the POMs missing."
fiRepository: gridsuite/study-server
Length of output: 5782
🌐 Web query:
powsybl-parent-ws 26.1 changelog
💡 Result:
As of May 28, 2026, there is no official release or changelog for a "powsybl-parent-ws 26.1" [1][2]. The PowSyBl project uses a release train system [2][3], and its versioning does not follow a "26.1" schema. For example, recent PowSyBl project releases have used formats like 2026.0.0 for dependencies [2] or specific version numbers for core components like 7.1.1 [4]. It is possible that "26.1" is being confused with other software releases from April/May 2026 that utilize that specific versioning, such as Webswing 26.1 [5] or Pip 26.1 [6]. If you are looking for configuration information for the powsybl-parent-ws Maven module, you can find the project repository on GitHub [1], where it serves as a parent POM providing Spring Boot and Jib integration for PowSyBl web service projects [1].
Citations:
- 1: https://github.com/powsybl/powsybl-parent
- 2: https://lfenergy.org/projects/powsybl/
- 3: https://lfenergy.org/powsybl-completes-another-release-train-fixing-bugs-and-adding-features/
- 4: https://github.com/powsybl/powsybl-core/releases/tag/v7.1.1
- 5: https://www.webswing.org/docs/26.1/overview/notes
- 6: https://www.infoq.com/news/2026/05/pip-261-dependency-cooldowns/?topicPageSponsorship=482b991b-52a4-4721-a036-83a2d7df92b8
🌐 Web query:
powsybl 26.1 release notes
💡 Result:
As of May 28, 2026, there is no "powsybl 26.1" release. The PowSyBl project operates on a release train schedule, and its current release is version 2026.0.0, which was released in April 2026 [1][2][3]. According to the official PowSyBl roadmap, the 2026.1 release train is planned for June 18, 2026 [1]. It is possible the query was confused with other software releases occurring in the same timeframe, such as Webswing 26.1 (released in April 2026) [4] or TURBOdesign Suite 2026.1 (released in May 2026) [5].
Citations:
- 1: https://github.com/powsybl/.github/wiki/Roadmap
- 2: https://github.com/powsybl/powsybl-dependencies/releases/tag/v2026.0.0
- 3: https://lfenergy.org/powsybl-community-releases-powsybl-dependencies-2026-0-0/
- 4: https://www.webswing.org/docs/26.1/overview/notes
- 5: https://www.openpr.com/news/4522418/software-release-turbodesign-suite-2026-1
Confirm Maven parent com.powsybl:powsybl-parent-ws:26.1 availability and assess impact (Spring Boot/Liquibase upgrades)
com.powsybl:powsybl-parent-ws:26.1 is published in Maven Central; however, the parent POM change is not trivial: it bumps maven.spring-boot.version from 3.4.9 → 3.5.11 and liquibase.version from 4.29.2 → 4.31.1. No specific 26.1 release notes/changelog were found, so validate compatibility by reviewing the parent POM impact and running the project’s test suite (including any DB/migration checks). (pom.xml, line 16)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@pom.xml` at line 16, Update and validate the parent POM change to
com.powsybl:powsybl-parent-ws:26.1 by confirming the artifact is resolvable in
your build environment, then assess impact of the bumped properties
maven.spring-boot.version (3.4.9→3.5.11) and liquibase.version (4.29.2→4.31.1)
by reviewing the parent POM for breaking changes and property overrides, running
the full test suite (unit, integration, and DB migration tests) and any
Liquibase changelog validations, and addressing incompatibilities (Spring Boot
or Liquibase API changes, dependency version conflicts, or migration behavior)
in the code or dependency management (e.g., overriding properties or updating
modules) until tests pass.
|
2 participants
Upgrade parent to v26.1