<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="/changelog.xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Looptro changelog</title>
    <link>https://looptro.dev/changelog</link>
    <atom:link href="https://looptro.dev/changelog.xml" rel="self" type="application/rss+xml"/>
    <description>New features, improvements, security fixes, and bug fixes in Looptro, the retrospective tool for teams.</description>
    <language>en</language>
    <item>
      <title>0.4.0: Slack and Linear connectors</title>
      <link>https://looptro.dev/changelog</link>
      <guid isPermaLink="false">looptro-changelog-0.4.0</guid>
      <pubDate>Wed, 05 Aug 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p>Send retro summaries to Slack, and turn action items into Linear issues that stay in sync.</p><p><strong>New features</strong></p><ul><li><strong>Export a retro summary to Slack</strong><br/>Connect Slack once, pick a channel, and post a retro summary there as a native Slack message. An admin connects the workspace; anyone on the team can export.</li><li><strong>Turn action items into Linear issues, kept in sync</strong><br/>Promote an action item to a Linear issue in your mapped team, with the assignee, due date, a backlink, and a retro label filled in. Status stays in sync both ways: change it in Looptro and it updates in Linear, change it in Linear and it flows back. Linked items show the real Linear workflow states.</li></ul><p><strong>Security fixes</strong></p><ul><li><strong>Connector tokens encrypted per team</strong><br/>Slack and Linear access tokens are stored encrypted under your team key, revoked when you disconnect, and never written to logs. Exporting sends the content to your own Slack/Linear workspace on your instruction.</li></ul>]]></description>
    </item>
    <item>
      <title>0.3.0: Retros on your phone</title>
      <link>https://looptro.dev/changelog/0.3.0</link>
      <guid isPermaLink="false">looptro-changelog-0.3.0</guid>
      <pubDate>Fri, 10 Jul 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p>Looptro now works on mobile, with friendlier docs and a changelog you can follow.</p><p><strong>Improvements</strong></p><ul><li><strong>Run a retro from your phone</strong><br/>The board, account settings, and every dialog now lay out cleanly on phones and small screens instead of overlapping or running off the edge.</li><li><strong>Docs sidebar and a changelog you can follow</strong><br/>The docs gained a sidebar with cross-page navigation and an on-page table of contents, and every release now has its own page plus an RSS feed you can subscribe to.</li></ul>]]></description>
    </item>
    <item>
      <title>0.2.0: Launch hardening</title>
      <link>https://looptro.dev/changelog/0.2.0</link>
      <guid isPermaLink="false">looptro-changelog-0.2.0</guid>
      <pubDate>Fri, 10 Jul 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p>Security and reliability work ahead of the public beta.</p><p><strong>Security fixes</strong></p><ul><li><strong>Hardened the app for public launch</strong><br/>Stricter browser security protections, session tokens hashed at rest, tighter production configuration, and a published vulnerability-disclosure policy at /.well-known/security.txt.</li></ul>]]></description>
    </item>
    <item>
      <title>0.1.0: Initial release</title>
      <link>https://looptro.dev/changelog/0.1.0</link>
      <guid isPermaLink="false">looptro-changelog-0.1.0</guid>
      <pubDate>Sun, 05 Jul 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p>Retrospectives for teams that turn into tracked action items, with AI agents as first-class participants.</p><p><strong>New features</strong></p><ul><li><strong>Action items that carry forward across retros</strong><br/>Action items are first-class objects, so last sprint's follow-ups show up in the next retro instead of getting lost in a doc.</li><li><strong>Bring AI agents into your retro over MCP</strong><br/>Claude Code, Cursor, and other MCP agents can read past retros, prep the board, and follow up on action items.</li><li><strong>Start a retro with no signup</strong><br/>Pick a template, share the link, and run the whole thing anonymously, with no account or email. Anonymous retros self-delete after 24 hours.</li><li><strong>Team accounts with social sign-in</strong><br/>Sign in with Google, Microsoft, GitHub, or GitLab for persistent team retros: unlimited history, async collection, the REST API and MCP server, audit log, and data export.</li><li><strong>Security and privacy built in</strong><br/>EU-hosted, encryption at rest, and self-serve GDPR data export and account deletion.</li></ul>]]></description>
    </item>
  </channel>
</rss>
