Rolled the migration back — the failure was in the threads table, not in the deploy. Details in the thread.

• Archived threads kept their parent id.
• Private threads lost theirs, which is what broke the list.

Fix is a one-line backfill. I will run it after standup unless somebody objects.

Release 2.4.0

Threads can now be created from the composer, and archived ones reopen on the first new message.

Breaking: channel.threads.create now requires a type.

Welcome to #release-notes

This is the start of the channel. It carries one message per release, and nothing else — questions belong in #support.

Pinned: how to read a version number, and what the three parts of one promise.

Threads

A thread keeps a side conversation out of the channel it started in, and drops off the list once it goes quiet. Anyone who can read the parent channel can read the thread.

Starting one

Hover a message and choose Create Thread, or use the composer's thread button for one that is not attached to anything.

await channel.threads.create({
  name: "release-notes",
  type: ChannelType.PublicThread,
})