chore(main): release testcontainers 4.0.0 - #433
Merged
totallyzen merged 1 commit intoMar 6, 2024
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Copy link
Copy Markdown
Member
|
Beep boop |
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
|
Do not merge until we have #426 EDIT: for keen eyes, the version above will update itself once we have the breaking change in place. |
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
Look, my year-old unreleased change! 😂 EDIT: ok, ok, it's technically in the 4.0.0rc2 |
Sorry, something went wrong.
github-actions
Bot
force-pushed
the
release-please--branches--main--components--testcontainers
branch
5 times, most recently
from
839d0b2 to
1f6fd43
Compare
March 5, 2024 22:10
totallyzen
added a commit
that referenced
this pull request
Mar 6, 2024
# change Set the version to the latest actual release candidate done by @alexanderankin. # Context In the first release-please PR #433 , we're not setting the version on the `pyproject.toml`, suspecting that it still works, but want to prove there are no issues with the automation. The easiest proof of this is to set the value in the file to the actual release candidate. `release-please` in the future will be able to do release candidates by running `release-please` from the command line (documentation to be made on this)
github-actions
Bot
force-pushed
the
release-please--branches--main--components--testcontainers
branch
2 times, most recently
from
4c51bd6 to
540f445
Compare
March 6, 2024 13:20
github-actions
Bot
force-pushed
the
release-please--branches--main--components--testcontainers
branch
from
540f445 to
498dc07
Compare
March 6, 2024 16:18
totallyzen
deleted the
release-please--branches--main--components--testcontainers
branch
March 6, 2024 16:40
Copy link
Copy Markdown
Contributor
Author
|
🤖 Release is at https://github.com/testcontainers/testcontainers-python/releases/tag/testcontainers-v4.0.0 🌻 |
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
4.0.0 (2024-03-06)
Release Notes
The breaking changes are the ones we were able to easily track. If you spot any new issues between 3.7.1 and 4.0.0, please do report it and we'll do our best to fix everything. The release is now
Some kudos from @totallyzen to folks who helped a great deal in starting things again:
⚠ BREAKING CHANGES
Features
Bug Fixes
Documentation
This PR was generated with Release Please. See documentation.