0.3.1

Bug fixes

• Fix processing of bot messages by updating to the latest Kafka models.

What's Changed

• DM-46782: Update dependencies for new Squarebot client by @rra in #11
• DM-46782: Prepare 0.3.1 release by @rra in #13

New Contributors

• @rra made their first contribution in #11

Full Changelog: 0.3.0...0.3.1

0.3.0

New features

• Unfurlbot now processes messages from other bots.

What's Changed

• DM-45383: Support unfurling Jira issue keys posted by apps like Sup by @jonathansick in #8

Full Changelog: 0.2.2...0.3.0

0.2.2

Bug fixes

• Make description optional in the JiraIssueSummmary model. Rubin epics typically do not have descriptions in the same manner as regular issues. Since we don't use the description field in the unfurl, we can safely make it optional.
• Normalize dates in the JiraIssueSummary so that they are consistently converted to the UTC timezone.
• Updated ProcessContext to call aclose rather than close on the Redis client.

Other changes

• Unfurlbot is now formatted with Ruff.
• Adopt uv and tox-uv for package installation and dependency resolution.

What's Changed

• DM-45338: Fix support for epics by @jonathansick in #7

Full Changelog: 0.2.1...0.2.2

0.2.1

Bug fixes

• Stop using the mrkdwn quote in the main unfurled content because it down't present well in mobile views.

What's Changed

• DM-43675: Stop using quote syntax in messages by @jonathansick in #5

Full Changelog: 0.2.0...0.2.1

0.2.0

New features

• Unfurlbot now uses Redis to store unfurl events and debounce unfurls to the same channel or thread. By default, Unfurlbot won't unfurl the same Jira issue to the same channel or thread more than once every 5 minutes. This can be configured with the UNFURLBOT_SLACK_DEBOUNCE_TIME environment variable.

What's Changed

• DM-43124: Add redis store of unfurl events to debounce replies by @jonathansick in #4

Full Changelog: 0.1.0...0.2.0

0.1.0

New features

• This is the first release of Unfurlbot. Unfurlbot listens to messages from Squarebot over Kafka and unfurls information about identifiers back to the conversation. At release, Unfurlbot supports unfurling Jira issue keys mentioned in Slack. Unfurlbot works with the Jira Data Proxy to fetch Jira issue information. On release, Unfurlbot is missing the following features:

  • Unfurls are not debounced, so Unfurlbot will respond with the same unfurl message in a conversation if it is mentioned several times.

  • Attachments are not scanned for content.

What's Changed

• DM-42877: Initial implementation by @jonathansick in #2

New Contributors

• @jonathansick made their first contribution in #2

Full Changelog: https://github.com/lsst-sqre/unfurlbot/commits/0.1.0