Skip to content

chore(next): release 0.17.0 - #521

Open
github-actions[bot] wants to merge 1 commit into
nextfrom
release-please--branches--next--components--plunk
Open

github-actions[bot] wants to merge 1 commit into
nextfrom
release-please--branches--next--components--plunk

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.17.0 (2026-10-18)

Features

  • add S3_PREFIX to store uploads under a folder in the bucket (fb0363f)
  • Add unsubscribedAt on email (0cbd5cb)
  • Add upgrade analytics dashboard (f9ba5e5)
  • Correctly identify rejection statuses on verification (d4621a9)
  • Enhanced campaign display (44b4b10)
  • Enhanced segment display (4774e38)
  • Enhanced templates display (c70cacf)
  • Enhanced workflow display (3d5bcb6)
  • Remove in-flow verification fee and default to off-session flow (b91ae18)
  • Show maximum 1 banner on home with additional details (209baee)

Bug Fixes

  • Add additional indexes to speed up analytics and search (ded0e3b)
  • Add invoice for verification charges (756d9f0)
  • Add lazy loading of email bodies to speed up activity feed (76b4efb)
  • api: keep username and TLS when parsing REDIS_URL for queues (d163865)
  • Harmonize deletion and confirmation modals (12f9f20)
  • Harmonize UI across various pages (8c8cbda)
  • release please configuration for MCP server (71969bd)
  • smtp: hot-reload renewed TLS certificates without restart (bc84b4a)
  • smtp: hot-reload renewed TLS certificates without restart (30a04a4)
  • smtp: pick up certificates issued after startup and harden reloads (873849c)

Documentation

  • warn that setting S3_PREFIX on an existing install breaks old uploads (a9350e5)

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot force-pushed the release-please--branches--next--components--plunk branch from a01a5de to 42e585f Compare October 9, 2026 18:30
@github-actions github-actions Bot changed the title chore(next): release 0.16.1 chore(next): release 0.17.0 Oct 9, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--next--components--plunk branch 12 times, most recently from 801312c to 9e8fc2a Compare October 15, 2026 06:22
@github-actions
github-actions Bot force-pushed the release-please--branches--next--components--plunk branch 3 times, most recently from 3efb724 to 39b3dda Compare October 17, 2026 09:12
@github-actions
github-actions Bot force-pushed the release-please--branches--next--components--plunk branch from 39b3dda to 2c3d020 Compare October 18, 2026 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants