-
Notifications
You must be signed in to change notification settings - Fork 253
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
fix: Add memcached container #322
fix: Add memcached container #322
Conversation
30a1f3e
to
c15abb3
Compare
@romulojales @pffijt Can you get this merged and released? |
c15abb3
to
2078179
Compare
Hello @damjankuznar , I just rebased the PR with the latest main version. Since I don't manage the project, I'm also waiting for the maintainers to review, and hopefully, approve my pr, so I could work with it without using my own fork. |
9f9e66a
to
9dadeb7
Compare
original commits are here - https://github.com/testcontainers/testcontainers-python/commits/romulojales/add-memcached |
🤖 I have created a release *beep* *boop* --- ## [4.4.1](testcontainers-v4.4.0...testcontainers-v4.4.1) (2024-05-14) ### Bug Fixes * Add memcached container ([#322](#322)) ([690b9b4](690b9b4)) * Add selenium video support [#6](#6) ([#364](#364)) ([3c8006c](3c8006c)) * **core:** add empty _configure to DockerContainer ([#556](#556)) ([08916c8](08916c8)) * **core:** remove version from compose tests ([#571](#571)) ([38946d4](38946d4)) * **keycloak:** add realm imports ([#565](#565)) ([f761b98](f761b98)) * **mysql:** Add seed support in MySQL ([#552](#552)) ([396079a](396079a)) * url quote passwords ([#549](#549)) ([6c5d227](6c5d227)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Adding Memcached container.
You have implemented a new container and would like to contribute it? Great! Here are the necessary steps.
__init__.py
) and corresponding tests.-e file:[feature name]
torequirements.in
and runmake requirements
. This command will find any new requirements and generate lock files to ensure reproducible builds (see the pip-tools documentation for details). Then runpip install -r requirements/[your python version].txt
to install the new requirements.README.rst
and add it to the table of contents (toctree
directive) in the top-levelREADME.rst
.[feature name]
to the list of components in the GitHub Action workflow in.github/workflows/main.yml
to run tests, build, and publish your package when pushed to themaster
branch.master
(or mergemaster
into your development branch).