Skip to content

[Snyk] Upgrade testcontainers from 10.28.0 to 11.0.3 #172

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nerdy-tech-com-gitub
Copy link
Owner

@nerdy-tech-com-gitub nerdy-tech-com-gitub commented Jul 18, 2025

snyk-top-banner

Snyk has created this PR to upgrade testcontainers from 10.28.0 to 11.0.3.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

  • The recommended version is 4 versions ahead of your current version.

  • The recommended version was released a month ago.

Release notes
Package name: testcontainers
  • 11.0.3 - 2025-06-10

    Changes

    🐛 Bug Fixes

    📦 Dependency Updates

  • 11.0.2 - 2025-06-07

    Changes

    🐛 Bug Fixes

  • 11.0.1 - 2025-06-06

    🐛 Bug Fixes

    📦 Dependency Updates

  • 11.0.0 - 2025-05-27

    🚨 Breaking Changes


    1. Minimum Node engine requirement set to 20.


    2. Default module images have been removed.

    Previously:

    await new PostgreSqlContainer().start();

    Now:

    await new PostgreSqlContainer("postgres:13.3-alpine").start();

    For convenience, here is a table of all the previous default values, which you could just copy/paste to get back working again, but have a think about which version you actually need. Some of these are quite old and need to be updated.

    Default module images
    Module Image
    arangodb arangodb:3.10.0
    azurecosmosdb mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:vnext-EN20250228
    azurite mcr.microsoft.com/azure-storage/azurite:3.33.0
    cassandra cassandra:5.0.2
    chromadb chromadb/chroma:0.6.3
    clickhouse clickhouse/clickhouse-server:25.3-alpine
    cockroachdb cockroachdb/cockroach:v24.3.5
    couchbase couchbase/server:6.5.1
    elasticsearch elasticsearch:7.17.7
    etcd quay.io/coreos/etcd:v3.6.0
    eventstoredb eventstore/eventstore:24.10
    gcloud gcr.io/google.com/cloudsdktool/cloud-sdk:517.0.0-emulators
    hivemq hivemq/hivemq-ce:2023.5
    k3s rancher/k3s:v1.31.2-k3s1
    kafka confluentinc/cp-kafka:7.2.2
    localstack localstack/localstack:2.2.0
    mariadb mariadb:11.5.2
    minio minio/minio:RELEASE.2024-12-13T22-19-12Z
    mockserver mockserver/mockserver:5.15.0
    mongodb mongo:4.0.1
    mssqlserver mcr.microsoft.com/mssql/server:2022-CU13-ubuntu-22.04
    mysql mysql:8.0.31
    nats nats:2.8.4-alpine
    neo4j neo4j:4.4.12
    ollama ollama/ollama:0.1.44
    postgresql postgres:13.3-alpine
    qdrant qdrant/qdrant:v1.13.4
    rabbitmq rabbitmq:3.12.11-management-alpine
    redis redis:7.2
    redpanda docker.redpanda.com/redpandadata/redpanda:v23.3.10
    scylladb scylladb/scylla:6.2.0
    selenium selenium/standalone-chrome:112.0
    toxiproxy ghcr.io/shopify/toxiproxy:2.11.0
    valkey valkey/valkey:8.0
    weaviate semitechnologies/weaviate:1.24.5

    3. Dropped support for Docker Compose v1 (EOL July 2023).


    4. Docker compose version no longer available via ComposeClient

    const { compose } = await getContainerRuntimeClient();
    compose.version; // no longer available

    5. Container stop timeouts have changed from seconds to milliseconds

    Previously:

    await container.stop({ timeout: 10 }); // 10 seconds

    Now:

    await container.stop({ timeout: 10_000 }); // 10 seconds

    6. EventStoreDB has been renamed to KurrentDB

    Previously:

    import { EventStoreDBContainer } from "@ testcontainers/eventstoredb";
    new EventStoreDBContainer("eventstore/eventstore:24.10").start();

    Now:

    import { KurrentDbContainer } from "@ testcontainers/kurrentdb";
    new KurrentDbContainer("kurrentplatform/kurrentdb:25.0").start();

    1. RandomUniquePortGenerator replaced by RandomPortGenerator

    Changes

    🧹 Maintenance

    📦 Dependency Updates

  • 10.28.0 - 2025-05-23

    Changes

    🚀 Features

    🐛 Bug Fixes

    🧹 Maintenance

from testcontainers GitHub release notes

Important

  • Warning: This PR contains a major version upgrade, and may be a breaking change.
  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Summary by Sourcery

Enhancements:

  • Bump testcontainers from ^10.9.0 to ^11.0.3

Snyk has created this PR to upgrade testcontainers from 10.28.0 to 11.0.3.

See this package in npm:
testcontainers

See this project in Snyk:
https://app.snyk.io/org/nerds-github/project/02f0e301-ca97-4c3b-9382-065289c73d9d?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

sourcery-ai bot commented Jul 18, 2025

Reviewer's Guide

Bump the testcontainers version in the JS client package to adopt the 11.0.3 release.

Class diagram for breaking changes in testcontainers v11 upgrade

classDiagram
    class PostgreSqlContainer {
      +constructor(image: string)
      +start()
    }
    class EventStoreDBContainer {
      <<removed>>
    }
    class KurrentDbContainer {
      +constructor(image: string)
      +start()
    }
    class ComposeClient {
      -version // removed
    }
    class RandomUniquePortGenerator {
      <<removed>>
    }
    class RandomPortGenerator {
      +generate()
    }

    EventStoreDBContainer <|-- KurrentDbContainer : renamed
    RandomUniquePortGenerator <|-- RandomPortGenerator : replaced
Loading

Class diagram for ComposeClient version property removal

classDiagram
    class ComposeClient {
      -version // property removed in v11
    }
Loading

File-Level Changes

Change Details Files
Upgrade testcontainers dependency to version 11.0.3
  • Replace the ^10.9.0 spec with ^11.0.3 in package.json
clients/js/package.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants