Skip to content

v0.26.1

Choose a tag to compare

View all tags
@heliocosta-dev heliocosta-dev released this 28 Oct 01:09
· 28 commits to main since this release
v0.26.1
f103438
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

MillionSend v0.26.1 is a maintenance release. Bcc recipients no longer travel inside the message handed to SES (#210), and the mail stack, Sentry and the AWS SDK move to their latest patch releases (#212). No database migrations.

Sending

  • Bcc stays out of the message (#210). The worker wrote a Bcc: header naming every Bcc recipient into the message it handed to SES. SES takes Bcc recipients from the send's destination list, so that header was never needed. It's gone, and Bcc recipients still get their copy.

Dependencies (#212)

  • Mail stack: nodemailer 10.2.1, mailauth 8.0.4 and smtp-server 3.21.1. Checked against the shipped code: outgoing messages come out byte for byte the same, and inbound DKIM, SPF, DMARC and ARC verdicts are unchanged.
  • Also: Sentry 11.9.0 (core, node, browser and the bundler plugins together), motion 14.6.0 and the AWS SDK clients 3.1156.0.
  • None of these updates fixes a published advisory.

Setup wizard

@millionsend/setup 0.9.3 is on npm. The wizard now prints the updates page's link instead of posting your address to it. Since v0.25.0 that form asks for Turnstile, so 0.9.2's post was refused. npx @millionsend/setup picks it up.

Upgrading a self-hosted instance

Pull the new image and restart. No migrations and no configuration changes. If you run the MX box, set MILLIONSEND_TAG=0.26.1 once the app runs this release, then pull and restart it.

Coming from v0.24.x or earlier? Read the v0.25.0 notes first. That release adds migrations 0063–0065; run them before up -d with docker compose run --rm --no-deps millionsend migrate.

Assets 2
Loading