Description
Assumption that database persistence required by Portal Frontend and other components like Portal Frontend Registration would be covered by the PostgreSQL 18.x (edit: this goal was changed from 17.x according to latest TRG updates and discussions with committers in November 2025) upgrade requested in the Portal Backend repository with eclipse-tractusx/portal-backend#1437
Otherwise please implement and track updates in separate sub-task issues.
See main issue eclipse-tractusx/sig-release#1501 for further details.
Test and Release Management will coordinate this activity.
Why it matters
- Confirms that Portal Frontend is reviewed for the PostgreSQL upgrade scope to ensure transparency in release tracking that this component does not require separate DB changes.
- Prevents confusion about whether the Portal Frontend was overlooked in upgrade planning.
Acceptance Criteria
- Verify that Portal Backend’s database upgrade to PostgreSQL 18.x sufficiently covers all persistence used by Portal Frontend.
- Otherwise please perform needed upgrades accordingly for Portal Frontend (see related parent issue and Portal Backend issue)
Notes
- This sub-task is for tracking and release documentation only.
Description
Assumption that database persistence required by Portal Frontend and other components like Portal Frontend Registration would be covered by the PostgreSQL 18.x (edit: this goal was changed from 17.x according to latest TRG updates and discussions with committers in November 2025) upgrade requested in the Portal Backend repository with eclipse-tractusx/portal-backend#1437
Otherwise please implement and track updates in separate sub-task issues.
See main issue eclipse-tractusx/sig-release#1501 for further details.
Test and Release Management will coordinate this activity.
Why it matters
Acceptance Criteria
Notes