Align PostgreSQL Testcontainers image version across integration tests

Open Beginner friendly
#5,383 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Tech stack
java, postgresql
Domain
databases, testing

Research direction

Inspect the four named Java integration test files and compare their PostgreSQL Testcontainers image declarations. Update the three files still using postgres:17.5 to postgres:18.1, then run the affected integration tests to confirm all four use the same image version.

Written by the indexing model from the issue text.

Description

in: build type: task

Problem

The PostgreSQL image version used in Testcontainers-based integration tests has
drifted between files. Currently:

  • postgres:18.1 is used in:

    • spring-batch-core/.../migration/PostgreSQLMigrationScriptIntegrationTests.java

  • postgres:17.5 is used in:

    • spring-batch-core/.../PostgreSQLJobRepositoryIntegrationTests.java
    • spring-batch-infrastructure/.../PostgresPagingQueryProviderIntegrationTests.java
    • spring-batch-samples/.../PostgreSQLJpaIntegrationTests.java

The drift was introduced in commit 0d1b5b103 ("Refine contribution #4954"),
which updated only the migration tests to postgres:18.1 while the other
three were left on postgres:17.5 from the earlier bulk upgrade in
commit 584c3c6ea (PR #4889, June 2025).

As a result, the migration scripts and the rest of the suite are validated
against different PostgreSQL major versions.

Proposed fix

Align all four files to postgres:18.1, matching the latest maintainer-chosen
version.

I would like to submit a PR for this.

Dominant language
Java
Stars
3k
Forks
2.5k
Avg merge
6d 53m
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from spring-projects/spring-batch

All issues in spring-projects/spring-batch

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.