Repository navigation
Releases: F3Nation-Community/slack-syncbot
Releases · F3Nation-Community/slack-syncbot
Release list
1.7.1
1.7.0
Added
- External Connections so two SyncBot installs can sync messages, files, and reactions
- Signed data migration export and import, including Export and Request Connection
- Settings Information section and a Workspace Block List for Team IDs
Changed
- Leave Connection pauses remote Workspaces, reconnecting restores them and shows
#channelnames - MySQL and PostgreSQL prefer
DATABASE_SCHEMAwithsyncbot_${stage}fallback - Federation returns 400 or 401 before reading an untrusted body
- File-part and JSON size follow this hop's injected HTTP cap
- After retention, the earliest-joined remaining local member becomes owner, or the group is disbanded
- A file share is the message itself, with the same from line as other messages
Removed
- Settings Broadcast allow-list
Fixed
- File shares keep the file up to Slack's 1 GB
- Threads, edits, and reactions follow the message across External Connections
#channelmentions stay a source#name (Workspace)- Hybrid reaction notices stay in the right thread with the mapped person's name
- Sync works after deploy without a Home Refresh
- A one-Workspace group offers Disband Group, not Leave Group
- Reactions keep the later add or remove
- Reinstall and import rejoin public Channels, leave private ones paused, and resume twin Channels on remaining Workspaces
- Create Connection and Import keep a wait screen and DM when they finish
- File copies keep a Slack ts when complete-upload omits it, including External Connections
- External Connection file parts follow the peer hop's advertised receive cap
- Cloud Run advertises a 30 MiB part cap
- The HTTP server finishes a Slack listener before the response
- A failed External Connection file reassembly returns
assemble_failedand does not ask for the parts again - A GIF stays on the message when that message also shares a file
1.6.2
Changed
- Code refactor; remove dead code, use verb prefixes for helpers, lockstep group invite Slack IDs
- Message and reaction sync skip Slack lookups until the channel has membership and publish targets
- File shares take the message ts from the upload response when present, then channel history
- Home tab reopen skips a rebuild when the content hash is unchanged
- User-token file shares keep the caption and Block Kit on the same native message as the file
- DEBUG logs include sync.* traces for message skip, pipeline fan-out, and file share ts
Fixed
- Pause Sync stops inbound until Resume
- User-token file shares skip inbound events by Slack file id and the share ts, so copies are not treated as new origins
- Reactions on a publishing Channel still fan out when the message is a synced copy; inbound creates stay skipped by echo and PostMeta
- Reactions and thread replies find existing messages by a six-decimal Slack ts, so older posts still match
- Thread replies Slack marks as a later share of a parent file still sync
- File-only bot shares record the share ts after Slack omits it on complete-upload, so thread replies still attach
1.6.1
Fixed
- Unlabeled source permalinks and Slack
message_mentionbecome amessage in #channel (Workspace)link; existing link text is left alone
1.6.0
Added
- Synced messages and ordinary file shares can post as the mapped person in the other workspace when they have authorized there
- A Channel can publish only, subscribe only, or both; a second publisher stays in the same channel sync until someone subscribes
- One Channel can subscribe to more than one distinct published Channel
- Reaction type Off does not apply incoming reaction add or remove on a subscribing Channel
Changed
- Authorize SyncBot no longer asks to send DMs as you
- New publishes are visible to the whole group; a Channel may be published in more than one group
- Reaction send and receive follow publish and subscribe; Reaction type is Hybrid, Direct, or Off
- Home Synced Channels lists each partner as a code-ticked
#channel (Workspace) - Home Synced Channels Status includes participation, for example Active (Publish and Subscribe)
- Home action buttons and in-channel sync notices lead with an emoji
Fixed
- Thread replies, files, and reactions stay on the original message's sync
- Unmapped people in synced messages render as Slack code, not literal backticks
1.5.4
Fixed
- Keep changelog tests aligned with shortened 1.2.0-length notes (#43)
1.5.3
Changed
- User Mapping leftover match names are gone (
matched_atismapped_at; old backup keys still import) TOKEN_ENCRYPTION_KEYstill loads whenDATA_ENCRYPTION_KEYis unset and logs a deprecation warning
1.5.2
Changed
- Synced message
#channelmentions become a code-ticked#name (Workspace), not a dest twin or a deep link
Fixed
- Mentions, source permalinks, and federation inbound follow the same mapping rules
- Dest Block Kit posts stay within Slack's block and section limits
- Threaded file shares use the matching dest timestamp
- AWS and GCP deploy keep previous secrets, default
syncbot_${stage}, and pass Slack scopes from env
1.5.1
Changed
- User Mapping uses map wording, a 20-row page, and
last_auto_map - Federation instance id is a SHA-256 fingerprint of the Ed25519 public key; connection codes carry the peer's full endpoint URL
- Sync hot paths reuse per-request and 60s process caches
Fixed
- Also-send-to-channel replies, hosted files, and file shares sync at the right thread level
- Block Kit bot posts keep newlines and emoji; unmapped mentions use a code-ticked display name
- On-the-fly mapping uses dest directory email then one
lookupByEmailand persists a none stub - Federation connection codes, image blocks, Lambda Function URLs, and mention rewrite work across instances
- AWS migrate reports FunctionError, Lambda timeout is 120s, and MySQL column CHANGE includes the existing type
- Leftover
SYNCBOT_INSTANCE_IDis ignored
1.5.0
Added
- User Mapping modal with Auto Map Now
- SyncBot posts in a Channel when it is published, even before anyone subscribes
Changed
- User Mapping opens from saved mappings; Auto Map Now runs in the background of the modal
- Failure DMs include a copyable details block
- New Channel syncs default to Hybrid reactions, listed first on Publish, Subscribe, and Edit
Fixed
- Users with the same email across Workspaces are mapped automatically
- Saving Edit on a Channel sync no longer times out the Lambda while listing every member