Repository navigation
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--master--components--emailengine-app
branch
6 times, most recently
from
November 4, 2026 21:20
0ab1bec to
66f9975
Compare
github-actions
Bot
force-pushed
the
release-please--branches--master--components--emailengine-app
branch
from
November 5, 2026 09:04
66f9975 to
708148e
Compare
Contributor
Author
|
🤖 Created releases: 🌻 |
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
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
2.87.1 (2026-11-05)
Summary
A reliability release. It stops a queued message from being sent twice when a send outlasts its timeout or a worker dies at the wrong moment, keeps exports alive across worker restarts, fixes the Docker health check for instances that serve the API over HTTPS, and keeps work that Redis refused for a moment instead of dropping it.
Who should upgrade
EENGINE_API_TLS. The image's health check probed a TLS port over plain HTTP, so Swarm never saw the task as healthy and replaced it every few minutes. This affected every release since 2.86.0.Breaking changes / action required
Highlights
text.hasMoreis set correctly when a multibyte or CRLF body is cut atmaxBytes.<Encryption>instead of<SSL>(IONOS) now set TLS correctly.emailengine passwordasks for a login right away instead of after a restart.Bug Fixes
This PR was generated with Release Please. See documentation.