<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Wicker Money changelog</title><description>What&apos;s shipped in Wicker Money, release by release.</description><link>https://wicker.money</link><language>en-us</language><item><title>v0.6.1 — owner confirmation and a table that fits</title><link>https://wicker.money/changelog/#0-6-1</link><guid isPermaLink="true">https://wicker.money/changelog/#0-6-1</guid><description>A small patch on v0.6.0. An owner is asked to confirm before a third-party plugin is switched on, the Transactions table fits narrower windows, the browser console and DevTools stop warning about the plugin frame, and one more row-level security policy gets the per-statement user lookup. There is one new migration, 033, which changes no access. **Back up your database before upgrading**, as for any release. See [Upgrading](https://wickermoney.dev/docs/self-hosting/upgrading#from-0-6-0).</description><pubDate>Fri, 23 Oct 2026 12:00:00 GMT</pubDate></item><item><title>v0.6.0 — plugin isolation and owner tooling</title><link>https://wicker.money/changelog/#0-6-0</link><guid isPermaLink="true">https://wicker.money/changelog/#0-6-0</guid><description>Plugin isolation, owner tooling and a performance and accessibility sweep. Insights and Spending Trends now run in sandboxed frames, the data export asks for your password again, owners can change roles and erase data from Settings, and a debt payoff plugin joins the bundled set. **Back up your database before upgrading.** This release has four migrations. Going back a version means running `down` four times, and that deletes the new debt payoff tables and their data. See [Upgrading](https://wickermoney.dev/docs/self-hosting/upgrading#from-0-5-0).</description><pubDate>Fri, 16 Oct 2026 12:00:00 GMT</pubDate></item><item><title>v0.5.0 — a sturdier plugin platform</title><link>https://wicker.money/changelog/#0-5-0</link><guid isPermaLink="true">https://wicker.money/changelog/#0-5-0</guid><description>Plugin platform hardening, plus account allowances. The theme is getting the plugin foundations right before more plugins are built on them: one shared contract for plugin server code, labelled stability for the plugin SDK, fewer duplicate requests, a way to name the instance&apos;s owner up front, and plainer wording about what a plugin is trusted to do. There is no breaking change for plugin authors. **Back up your database before upgrading.** Both of this release&apos;s database changes can be undone, so going back to 0.4.2 doesn&apos;t need the backup, but it&apos;s still the safe habit.</description><pubDate>Sat, 10 Oct 2026 12:00:00 GMT</pubDate></item><item><title>v0.4.2 — made for phones</title><link>https://wicker.money/changelog/#0-4-2</link><guid isPermaLink="true">https://wicker.money/changelog/#0-4-2</guid><description>Wicker Money now works on a phone, with tidier lists everywhere and a round of accessibility fixes. No database changes, so upgrading is a pull and a restart, and going back to 0.4.1 is just running the old image.</description><pubDate>Tue, 06 Oct 2026 12:00:00 GMT</pubDate></item><item><title>v0.4.1 — two new starter categories</title><link>https://wicker.money/changelog/#0-4-1</link><guid isPermaLink="true">https://wicker.money/changelog/#0-4-1</guid><description>Two more categories in the starter set. No database changes, so upgrading is a pull and a restart, and going back to 0.4.0 is just running the old image.</description><pubDate>Mon, 05 Oct 2026 12:00:00 GMT</pubDate></item><item><title>v0.4.0 — plugins you can turn on and off</title><link>https://wicker.money/changelog/#0-4-0</link><guid isPermaLink="true">https://wicker.money/changelog/#0-4-0</guid><description>Pick the plugins your instance runs, match payments straight from your transactions, and see form mistakes right where you made them. **Back up your database before upgrading.** Both of this release&apos;s database changes can be undone, so going back to 0.3.0 doesn&apos;t need the backup, but it&apos;s still the safe habit.</description><pubDate>Sun, 04 Oct 2026 12:00:00 GMT</pubDate></item><item><title>v0.3.0 — did it land?</title><link>https://wicker.money/changelog/#0-3-0</link><guid isPermaLink="true">https://wicker.money/changelog/#0-3-0</guid><description>Tell Wicker Money when a paycheck or bill actually posts, and it stops counting it as still to come. Plus budgets that cover a stretch of time instead of a single month. **Back up your database before upgrading:** going back to 0.2.1 means restoring that backup. Needs PostgreSQL 15 or later; 16 was already the minimum.</description><pubDate>Sat, 03 Oct 2026 12:00:00 GMT</pubDate></item><item><title>v0.2.1 — the forecast</title><link>https://wicker.money/changelog/#0-2-1</link><guid isPermaLink="true">https://wicker.money/changelog/#0-2-1</guid><description>See where an account is heading, not just where it is. No database changes, so upgrading from 0.2.0 is a pull and a restart. Afterwards, open **Settings → Time zone**.</description><pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate></item><item><title>v0.2.0 — recurring items and Until payday</title><link>https://wicker.money/changelog/#0-2-0</link><guid isPermaLink="true">https://wicker.money/changelog/#0-2-0</guid><description>Tell Wicker Money what you expect to come in and go out, and it tells you whether you&apos;ll make it to payday. **Back up your database before upgrading:** this release reshapes how recurring items are stored, and going back to 0.1.0 means restoring that backup.</description><pubDate>Fri, 02 Oct 2026 12:00:00 GMT</pubDate></item><item><title>v0.1.0 — the first release</title><link>https://wicker.money/changelog/#0-1-0</link><guid isPermaLink="true">https://wicker.money/changelog/#0-1-0</guid><description>The first tagged release: everything you need to run Wicker Money on your own server, import your history and see where your money goes. Curated from the repo&apos;s own [CHANGELOG.md](https://github.com/wickermoney/wicker-money/blob/main/CHANGELOG.md).</description><pubDate>Mon, 28 Sep 2026 12:00:00 GMT</pubDate></item></channel></rss>