Bump test-containers.version from 1.15.3 to 1.16.1

[dependabot]

Bumps test-containers.version from 1.15.3 to 1.16.1.
Updates testcontainers from 1.15.3 to 1.16.1

Release notes

Sourced from testcontainers's releases.

1.16.1

What's Changed

Testcontainers 1.16.1 has been released! 🎉

This release brings a lot of eagerly awaited new features and fixes, such as:

🔮 Better Oracle Database support

Thanks to the engagement of the community and @​gvenzl's new Docker images for Oracle Database Express Edition we were able to update our OracleContainer module to ensure its compatibility with a wide range of Oracle XE versions.

And at the same time, thanks to the new images, we were able to re-integrate the Oracle module into our CI. This means we can verify compatibility for using Testcontainers with Oracle Database going forward.

☁️ New Azure Cosmos DB module

With the new Azure Comos DB module we finally added Azure to our list of cloud service testing facilities. It is based on Microsoft's Azure Cosmos DB-Emulator and provides you with a way to do your integration testing without the need for an actual Azure service.

public CosmosDBEmulatorContainer emulator = new CosmosDBEmulatorContainer(
        DockerImageName.parse("mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:latest")
);

Please check out the module docs to learn how to use it for your integration testing needs.

⛴ Host port access for containers

For further improving the developer experience of our users, we added a new API to make hosts ports accessible to containers:

container.withAccessToHost(true)

You still need to use exposeHostPorts, as per the docs, but this can now be done after the container has started, thereby allowing new usage patterns in your tests.

🌪 Faster Cassandra startup

By making clever use of the configuration settings available in Cassandra, CassandraContainer will now start up to 3 times faster. It is now also configured to be less resource hungry out of the box.

✨ Better startup performance for all containers

We found a couple of ways to improve the container startup performance for our users, no matter the Testcontainers module you use. This comes through some internal changes with regards to how Testcontainers checks for open ports during container startup and will shave up to a couple of seconds from your test suite.

---

We are grateful for the ongoing support of our community and users and thank each of our awesome contributors!

... (truncated)

Commits

• 81317a6 Provide an API to force access to the host (#4584)
• 2174928 Remove unused @ClassRule container in KafkaContainerTest and use `cp-kafk...
• 737865f Upgrade ryuk image to 0.3.3 (#4581)
• 69cf13c Perform port checks in parallel (#4463)
• b29716d Remove httpclient5_test (#4562)
• b7e9bb6 Update GitLab CI docs: Add --tls=false to docker-in-docker to avoid startup d...
• 92155d9 Temporarily disable Thundra on master branch (#4570)
• 1ad2a05 Add Azure Cosmos DB module: Introduce CosmosDBEmulatorContainer (#4303)
• 8d40cbd Enable JUnitPlatform for Spock tests (#4568)
• f31ee79 Skip japicmp for new modules (#4569)
• Additional commits viewable in compare view

Updates oracle-xe from 1.15.3 to 1.16.1

Release notes

Sourced from oracle-xe's releases.

1.16.1

What's Changed

Testcontainers 1.16.1 has been released! 🎉

This release brings a lot of eagerly awaited new features and fixes, such as:

🔮 Better Oracle Database support

Thanks to the engagement of the community and @​gvenzl's new Docker images for Oracle Database Express Edition we were able to update our OracleContainer module to ensure its compatibility with a wide range of Oracle XE versions.

And at the same time, thanks to the new images, we were able to re-integrate the Oracle module into our CI. This means we can verify compatibility for using Testcontainers with Oracle Database going forward.

☁️ New Azure Cosmos DB module

With the new Azure Comos DB module we finally added Azure to our list of cloud service testing facilities. It is based on Microsoft's Azure Cosmos DB-Emulator and provides you with a way to do your integration testing without the need for an actual Azure service.

public CosmosDBEmulatorContainer emulator = new CosmosDBEmulatorContainer(
        DockerImageName.parse("mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:latest")
);

Please check out the module docs to learn how to use it for your integration testing needs.

⛴ Host port access for containers

For further improving the developer experience of our users, we added a new API to make hosts ports accessible to containers:

container.withAccessToHost(true)

You still need to use exposeHostPorts, as per the docs, but this can now be done after the container has started, thereby allowing new usage patterns in your tests.

🌪 Faster Cassandra startup

By making clever use of the configuration settings available in Cassandra, CassandraContainer will now start up to 3 times faster. It is now also configured to be less resource hungry out of the box.

✨ Better startup performance for all containers

We found a couple of ways to improve the container startup performance for our users, no matter the Testcontainers module you use. This comes through some internal changes with regards to how Testcontainers checks for open ports during container startup and will shave up to a couple of seconds from your test suite.

---

We are grateful for the ongoing support of our community and users and thank each of our awesome contributors!

... (truncated)

Commits

• 81317a6 Provide an API to force access to the host (#4584)
• 2174928 Remove unused @ClassRule container in KafkaContainerTest and use `cp-kafk...
• 737865f Upgrade ryuk image to 0.3.3 (#4581)
• 69cf13c Perform port checks in parallel (#4463)
• b29716d Remove httpclient5_test (#4562)
• b7e9bb6 Update GitLab CI docs: Add --tls=false to docker-in-docker to avoid startup d...
• 92155d9 Temporarily disable Thundra on master branch (#4570)
• 1ad2a05 Add Azure Cosmos DB module: Introduce CosmosDBEmulatorContainer (#4303)
• 8d40cbd Enable JUnitPlatform for Spock tests (#4568)
• f31ee79 Skip japicmp for new modules (#4569)
• Additional commits viewable in compare view

Updates mysql from 1.15.3 to 1.16.1

Release notes

Sourced from mysql's releases.

1.16.1

What's Changed

Testcontainers 1.16.1 has been released! 🎉

This release brings a lot of eagerly awaited new features and fixes, such as:

🔮 Better Oracle Database support

Thanks to the engagement of the community and @​gvenzl's new Docker images for Oracle Database Express Edition we were able to update our OracleContainer module to ensure its compatibility with a wide range of Oracle XE versions.

And at the same time, thanks to the new images, we were able to re-integrate the Oracle module into our CI. This means we can verify compatibility for using Testcontainers with Oracle Database going forward.

☁️ New Azure Cosmos DB module

With the new Azure Comos DB module we finally added Azure to our list of cloud service testing facilities. It is based on Microsoft's Azure Cosmos DB-Emulator and provides you with a way to do your integration testing without the need for an actual Azure service.

public CosmosDBEmulatorContainer emulator = new CosmosDBEmulatorContainer(
        DockerImageName.parse("mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:latest")
);

Please check out the module docs to learn how to use it for your integration testing needs.

⛴ Host port access for containers

For further improving the developer experience of our users, we added a new API to make hosts ports accessible to containers:

container.withAccessToHost(true)

You still need to use exposeHostPorts, as per the docs, but this can now be done after the container has started, thereby allowing new usage patterns in your tests.

🌪 Faster Cassandra startup

By making clever use of the configuration settings available in Cassandra, CassandraContainer will now start up to 3 times faster. It is now also configured to be less resource hungry out of the box.

✨ Better startup performance for all containers

We found a couple of ways to improve the container startup performance for our users, no matter the Testcontainers module you use. This comes through some internal changes with regards to how Testcontainers checks for open ports during container startup and will shave up to a couple of seconds from your test suite.

---

We are grateful for the ongoing support of our community and users and thank each of our awesome contributors!

... (truncated)

Commits

• 81317a6 Provide an API to force access to the host (#4584)
• 2174928 Remove unused @ClassRule container in KafkaContainerTest and use `cp-kafk...
• 737865f Upgrade ryuk image to 0.3.3 (#4581)
• 69cf13c Perform port checks in parallel (#4463)
• b29716d Remove httpclient5_test (#4562)
• b7e9bb6 Update GitLab CI docs: Add --tls=false to docker-in-docker to avoid startup d...
• 92155d9 Temporarily disable Thundra on master branch (#4570)
• 1ad2a05 Add Azure Cosmos DB module: Introduce CosmosDBEmulatorContainer (#4303)
• 8d40cbd Enable JUnitPlatform for Spock tests (#4568)
• f31ee79 Skip japicmp for new modules (#4569)
• Additional commits viewable in compare view

Updates postgresql from 1.15.3 to 1.16.1

Release notes

Sourced from postgresql's releases.

1.16.1

What's Changed

Testcontainers 1.16.1 has been released! 🎉

This release brings a lot of eagerly awaited new features and fixes, such as:

🔮 Better Oracle Database support

Thanks to the engagement of the community and @​gvenzl's new Docker images for Oracle Database Express Edition we were able to update our OracleContainer module to ensure its compatibility with a wide range of Oracle XE versions.

And at the same time, thanks to the new images, we were able to re-integrate the Oracle module into our CI. This means we can verify compatibility for using Testcontainers with Oracle Database going forward.

☁️ New Azure Cosmos DB module

With the new Azure Comos DB module we finally added Azure to our list of cloud service testing facilities. It is based on Microsoft's Azure Cosmos DB-Emulator and provides you with a way to do your integration testing without the need for an actual Azure service.

public CosmosDBEmulatorContainer emulator = new CosmosDBEmulatorContainer(
        DockerImageName.parse("mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:latest")
);

Please check out the module docs to learn how to use it for your integration testing needs.

⛴ Host port access for containers

For further improving the developer experience of our users, we added a new API to make hosts ports accessible to containers:

container.withAccessToHost(true)

You still need to use exposeHostPorts, as per the docs, but this can now be done after the container has started, thereby allowing new usage patterns in your tests.

🌪 Faster Cassandra startup

By making clever use of the configuration settings available in Cassandra, CassandraContainer will now start up to 3 times faster. It is now also configured to be less resource hungry out of the box.

✨ Better startup performance for all containers

We found a couple of ways to improve the container startup performance for our users, no matter the Testcontainers module you use. This comes through some internal changes with regards to how Testcontainers checks for open ports during container startup and will shave up to a couple of seconds from your test suite.

---

We are grateful for the ongoing support of our community and users and thank each of our awesome contributors!

... (truncated)

Commits

• 81317a6 Provide an API to force access to the host (#4584)
• 2174928 Remove unused @ClassRule container in KafkaContainerTest and use `cp-kafk...
• 737865f Upgrade ryuk image to 0.3.3 (#4581)
• 69cf13c Perform port checks in parallel (#4463)
• b29716d Remove httpclient5_test (#4562)
• b7e9bb6 Update GitLab CI docs: Add --tls=false to docker-in-docker to avoid startup d...
• 92155d9 Temporarily disable Thundra on master branch (#4570)
• 1ad2a05 Add Azure Cosmos DB module: Introduce CosmosDBEmulatorContainer (#4303)
• 8d40cbd Enable JUnitPlatform for Spock tests (#4568)
• f31ee79 Skip japicmp for new modules (#4569)
• Additional commits viewable in compare view

Updates mssqlserver from 1.15.3 to 1.16.1

Release notes

Sourced from mssqlserver's releases.

1.16.1

What's Changed

Testcontainers 1.16.1 has been released! 🎉

This release brings a lot of eagerly awaited new features and fixes, such as:

🔮 Better Oracle Database support

Thanks to the engagement of the community and @​gvenzl's new Docker images for Oracle Database Express Edition we were able to update our OracleContainer module to ensure its compatibility with a wide range of Oracle XE versions.

And at the same time, thanks to the new images, we were able to re-integrate the Oracle module into our CI. This means we can verify compatibility for using Testcontainers with Oracle Database going forward.

☁️ New Azure Cosmos DB module

With the new Azure Comos DB module we finally added Azure to our list of cloud service testing facilities. It is based on Microsoft's Azure Cosmos DB-Emulator and provides you with a way to do your integration testing without the need for an actual Azure service.

public CosmosDBEmulatorContainer emulator = new CosmosDBEmulatorContainer(
        DockerImageName.parse("mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:latest")
);

Please check out the module docs to learn how to use it for your integration testing needs.

⛴ Host port access for containers

For further improving the developer experience of our users, we added a new API to make hosts ports accessible to containers:

container.withAccessToHost(true)

You still need to use exposeHostPorts, as per the docs, but this can now be done after the container has started, thereby allowing new usage patterns in your tests.

🌪 Faster Cassandra startup

By making clever use of the configuration settings available in Cassandra, CassandraContainer will now start up to 3 times faster. It is now also configured to be less resource hungry out of the box.

✨ Better startup performance for all containers

We found a couple of ways to improve the container startup performance for our users, no matter the Testcontainers module you use. This comes through some internal changes with regards to how Testcontainers checks for open ports during container startup and will shave up to a couple of seconds from your test suite.

---

We are grateful for the ongoing support of our community and users and thank each of our awesome contributors!

... (truncated)

Commits

• 81317a6 Provide an API to force access to the host (#4584)
• 2174928 Remove unused @ClassRule container in KafkaContainerTest and use `cp-kafk...
• 737865f Upgrade ryuk image to 0.3.3 (#4581)
• 69cf13c Perform port checks in parallel (#4463)
• b29716d Remove httpclient5_test (#4562)
• b7e9bb6 Update GitLab CI docs: Add --tls=false to docker-in-docker to avoid startup d...
• 92155d9 Temporarily disable Thundra on master branch (#4570)
• 1ad2a05 Add Azure Cosmos DB module: Introduce CosmosDBEmulatorContainer (#4303)
• 8d40cbd Enable JUnitPlatform for Spock tests (#4568)
• f31ee79 Skip japicmp for new modules (#4569)
• Additional commits viewable in compare view

Updates mongodb from 1.15.3 to 1.16.1

Release notes

Sourced from mongodb's releases.

1.16.1

What's Changed

Testcontainers 1.16.1 has been released! 🎉

This release brings a lot of eagerly awaited new features and fixes, such as:

🔮 Better Oracle Database support

Thanks to the engagement of the community and @​gvenzl's new Docker images for Oracle Database Express Edition we were able to update our OracleContainer module to ensure its compatibility with a wide range of Oracle XE versions.

And at the same time, thanks to the new images, we were able to re-integrate the Oracle module into our CI. This means we can verify compatibility for using Testcontainers with Oracle Database going forward.

☁️ New Azure Cosmos DB module

With the new Azure Comos DB module we finally added Azure to our list of cloud service testing facilities. It is based on Microsoft's Azure Cosmos DB-Emulator and provides you with a way to do your integration testing without the need for an actual Azure service.

public CosmosDBEmulatorContainer emulator = new CosmosDBEmulatorContainer(
        DockerImageName.parse("mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:latest")
);

Please check out the module docs to learn how to use it for your integration testing needs.

⛴ Host port access for containers

For further improving the developer experience of our users, we added a new API to make hosts ports accessible to containers:

container.withAccessToHost(true)

You still need to use exposeHostPorts, as per the docs, but this can now be done after the container has started, thereby allowing new usage patterns in your tests.

🌪 Faster Cassandra startup

By making clever use of the configuration settings available in Cassandra, CassandraContainer will now start up to 3 times faster. It is now also configured to be less resource hungry out of the box.

✨ Better startup performance for all containers

We found a couple of ways to improve the container startup performance for our users, no matter the Testcontainers module you use. This comes through some internal changes with regards to how Testcontainers checks for open ports during container startup and will shave up to a couple of seconds from your test suite.

---

We are grateful for the ongoing support of our community and users and thank each of our awesome contributors!

... (truncated)

Commits

• 81317a6 Provide an API to force access to the host (#4584)
• 2174928 Remove unused @ClassRule container in KafkaContainerTest and use `cp-kafk...
• 737865f Upgrade ryuk image to 0.3.3 (#4581)
• 69cf13c Perform port checks in parallel (#4463)
• b29716d Remove httpclient5_test (#4562)
• b7e9bb6 Update GitLab CI docs: Add --tls=false to docker-in-docker to avoid startup d...
• 92155d9 Temporarily disable Thundra on master branch (#4570)
• 1ad2a05 Add Azure Cosmos DB module: Introduce CosmosDBEmulatorContainer (#4303)
• 8d40cbd Enable JUnitPlatform for Spock tests (#4568)
• f31ee79 Skip japicmp for new modules (#4569)
• Additional commits viewable in compare view

Updates solr from 1.15.3 to 1.16.1

Release notes

Sourced from solr's releases.

1.16.1

What's Changed

Testcontainers 1.16.1 has been released! 🎉

This release brings a lot of eagerly awaited new features and fixes, such as:

🔮 Better Oracle Database support

Thanks to the engagement of the community and @​gvenzl's new Docker images for Oracle Database Express Edition we were able to update our OracleContainer module to ensure its compatibility with a wide range of Oracle XE versions.

And at the same time, thanks to the new images, we were able to re-integrate the Oracle module into our CI. This means we can verify compatibility for using Testcontainers with Oracle Database going forward.

☁️ New Azure Cosmos DB module

With the new Azure Comos DB module we finally added Azure to our list of cloud service testing facilities. It is based on Microsoft's Azure Cosmos DB-Emulator and provides you with a way to do your integration testing without the need for an actual Azure service.

public CosmosDBEmulatorContainer emulator = new CosmosDBEmulatorContainer(
        DockerImageName.parse("mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:latest")
);

Please check out the module docs to learn how to use it for your integration testing needs.

⛴ Host port access for containers

For further improving the developer experience of our users, we added a new API to make hosts ports accessible to containers:

container.withAccessToHost(true)

You still need to use exposeHostPorts, as per the docs, but this can now be done after the container has started, thereby allowing new usage patterns in your tests.

🌪 Faster Cassandra startup

By making clever use of the configuration settings available in Cassandra, CassandraContainer will now start up to 3 times faster. It is now also configured to be less resource hungry out of the box.

✨ Better startup performance for all containers

We found a couple of ways to improve the container startup performance for our users, no matter the Testcontainers module you use. This comes through some internal changes with regards to how Testcontainers checks for open ports during container startup and will shave up to a couple of seconds from your test suite.

---

We are grateful for the ongoing support of our community and users and thank each of our awesome contributors!

... (truncated)

Commits

• 81317a6 Provide an API to force access to the host (#4584)
• 2174928 Remove unused @ClassRule container in KafkaContainerTest and use `cp-kafk...
• 737865f Upgrade ryuk image to 0.3.3 (#4581)
• 69cf13c Perform port checks in parallel (#4463)
• b29716d Remove httpclient5_test (#4562)
• b7e9bb6 Update GitLab CI docs: Add --tls=false to docker-in-docker to avoid startup d...
• 92155d9 Temporarily disable Thundra on master branch (#4570)
• 1ad2a05 Add Azure Cosmos DB module: Introduce CosmosDBEmulatorContainer (#4303)
• 8d40cbd Enable JUnitPlatform for Spock tests (#4568)
• f31ee79 Skip japicmp for new modules (#4569)
• Additional commits viewable in compare view

Updates elasticsearch from 1.15.3 to 1.16.1

Release notes

Sourced from elasticsearch's releases.

1.16.1

What's Changed

Testcontainers 1.16.1 has been released! 🎉

This release brings a lot of eagerly awaited new features and fixes, such as:

🔮 Better Oracle Database support

Thanks to the engagement of the community and @​gvenzl's new Docker images for Oracle Database Express Edition we were able to update our OracleContainer module to ensure its compatibility with a wide range of Oracle XE versions.

And at the same time, thanks to the new images, we were able to re-integrate the Oracle module into our CI. This means we can verify compatibility for using Testcontainers with Oracle Database going forward.

☁️ New Azure Cosmos DB module

With the new Azure Comos DB module we finally added Azure to our list of cloud service testing facilities. It is based on Microsoft's Azure Cosmos DB-Emulator and provides you with a way to do your integration testing without the need for an actual Azure service.

public CosmosDBEmulatorContainer emulator = new CosmosDBEmulatorContainer(
        DockerImageName.parse("mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:latest")
);

Please check out the module docs to learn how to use it for your integration testing needs.

⛴ Host port access for containers

For further improving the developer experience of our users, we added a new API to make hosts ports accessible to containers:

container.withAccessToHost(true)

You still need to use exposeHostPorts, as per the docs, but this can now be done after the container has started, thereby allowing new usage patterns in your tests.

🌪 Faster Cassandra startup

By making clever use of the configuration settings available in Cassandra, CassandraContainer will now start up to 3 times faster. It is now also configured to be less resource hungry out of the box.

✨ Better startup performance for all containers

We found a couple of ways to improve the container startup performance for our users, no matter the Testcontainers module you use. This comes through some internal changes with regards to how Testcontainers checks for open ports during container startup and will shave up to a couple of seconds from your test suite.

---

We are grateful for the ongoing support of our community and users and thank each of our awesome contributors!

... (truncated)

Commits

• 81317a6 Provide an API to force access to the host (#4584)
• 2174928 Remove unused @ClassRule container in KafkaContainerTest and use `cp-kafk...
• 737865f Upgrade ryuk image to 0.3.3 (#4581)
• 69cf13c Perform port checks in parallel (#4463)
• b29716d Remove httpclient5_test (#4562)
• b7e9bb6 Update GitLab CI docs: Add --tls=false to docker-in-docker to avoid startup d...
• 92155d9 Temporarily disable Thundra on master branch (#4570)
• 1ad2a05 Add Azure Cosmos DB module: Introduce CosmosDBEmulatorContainer (#4303)
• 8d40cbd Enable JUnitPlatform for Spock tests (#4568)
• f31ee79 Skip japicmp for new modules (#4569)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[dependabot]

Superseded by #655.