Skip to content

v0.36.0

Latest
Latest
Compare
Choose a tag to compare
@github-actions github-actions released this 27 Mar 12:11
· 25 commits to refs/heads/main since this release
v0.36.0
a0e3b71

What's Changed

⚠️ Breaking Changes

  • feat(azure)!: add Azurite, EventHubs and ServiceBus in the new Azure module, deprecating the old Azurite module (#3008) @mdelapenya

Users of the old Azurite module must update their code to use the new Azure module instead, which contains the same functionality under the azurite sub-package.
We took this opportunity to remove the unnecessarily exported Settings field from the Azurite container type,
so users of the Azurite container type must update their code to simply do not use that field.

  • chore(deps)!: bump github.com/docker/docker from 27.1.1+incompatible to 28.0.1+incompatible (#3017) @dependabot[bot]

Bumping the Docker package to a newer major version came with lots of benefits, but also some breaking changes. For that reason, users of the following
container methods and types must update their code to use the new types and methods instead:

  • Container.Inspect: the return type has been changed from types.ContainerJSON to container.InspectResponse.
  • Container.State: the return type has been changed from types.ContainerState to container.State.
  • DockerProvider.ContainerFromType: the method signature has been changed to accept a container.Summary instead of a types.Container.
    At the same time, if consuming Docker types or methods, users must update their code to use the new types and methods instead.
    As a good rule of thumb, users of the "github.com/docker/docker/api/types" package must update their code to use "github.com/docker/docker/api/types/container" instead.

Users of the deprecated DockerCompose type from the compose module must update their code to use DockerComposer instead.
The former unexported dockerCompose type has been renamed to DockerCompose. This breaking change was done because returning
an un-exported type from a constructor function limits the flexibility and usability of the returned instance. Callers could use
the exported methods, but could not declare variables of that type, pass instances to other functions, or embed them in structs
without exposing the constructor itself. This breaking change was needed to improve the usability of the compose module.

Users of the testcontainers.Logging variable and the testcontainers.TestLogger function must update their code to use the new log.Default() logger instance and the log.TestLogger() function instead, and
users of the testcontainers.Logger interface must update their code to use the new log.Logger interface instead.
The new log package allows users to set a custom logger instance calling the log.SetDefault(l log.Logger) function.
This breaking change was needed to improve the usability of the logging functionality when using the testcontainers package.

Users of the NATS module and the ConnectionString type must remove the variadic arguments from the ConnectionString method. This breaking change was needed because those arguments weren't in use.

  • chore!: rename EnpointSettingsModifier to EndpointSettingsModifier (#2941) @NathanBaulch

We fixed a typo in the exported field of the ContainerRequest struct, so users of the EnpointSettingsModifier type must update their code to use the EndpointSettingsModifier type instead.

🔒 Security

  • chore(deps): bump golang.org/x/net from 0.23.0 to 0.36.0 in /modules/dynamodb (#3059) @mdelapenya
  • chore(deps): bump golang.org/x/net from 0.23.0 to 0.36.0 in /modules/scylladb (#3058) @dependabot[bot]
  • chore(deps): bump golang.org/x/net from 0.23.0 to 0.36.0 in /modules/databend (#3055) @dependabot[bot]
  • chore(deps): bump golang.org/x/net from 0.26.0 to 0.33.0 (#2961) @dependabot[bot]

🚀 Features

🐛 Bug Fixes

📖 Documentation

🧹 Housekeeping

📦 Dependency updates

Contributors

stevenh, NathanBaulch, and 11 other contributors
Assets 2
Loading