<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Changelog on BunnyCal Blog</title><link>https://bunnycal.io/blog/tags/changelog/</link><description>Recent content in Changelog on BunnyCal Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 27 Jul 2026 16:03:00 +0530</lastBuildDate><atom:link href="https://bunnycal.io/blog/tags/changelog/index.xml" rel="self" type="application/rss+xml"/><item><title>What shipped in July</title><link>https://bunnycal.io/blog/changelog-july-2026/</link><pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate><guid>https://bunnycal.io/blog/changelog-july-2026/</guid><description>&lt;p&gt;A month of work that mostly amounts to removing steps from things you already
do more than once a day.&lt;/p&gt;
&lt;h2 id="multi-account-calendars"&gt;Multi-account calendars&lt;/h2&gt;
&lt;p&gt;You can now connect more than one calendar account per provider — two Google
accounts, or a Google and a Microsoft account side by side. Every connected
calendar can be marked as a conflict source, while exactly one stays the write
target for new bookings.&lt;/p&gt;
&lt;p&gt;This also fixes a long-standing sharp edge: connecting a second account used to
overwrite the first. Each connection is now independent, with its own disconnect.&lt;/p&gt;</description></item></channel></rss>