From 28fec83b8c8e7e457a9db4ca3e799b4221d9fa99 Mon Sep 17 00:00:00 2001
From: Robert Field <robertfield@quadrimular.com>
Date: Wed, 13 May 2026 18:04:19 +0100
Subject: [PATCH] fix: re-release after revert of PR #89

The revert in PR #93 used GitHub's default revert UI, which produced a
commit message of `Revert "feat: ..."` without a `revert:` prefix or
`This reverts commit <hash>.` footer. semantic-release's commit-analyzer
therefore skipped the commit ("The commit should not trigger a release")
and no version was published, leaving the reverted code unreleased on
npm.

This empty commit re-triggers semantic-release so the revert ships as a
patch release.