- Fix the MetaGer key staying behind as a browser cookie while anonymous token were active, which meant searches kept being charged to the key
- Fix stored search settings getting lost when settings storage in the extension was switched back off
- Fix the websocket for key balance updates connecting to a host chosen at build time rather than the MetaGer the search went to
- Fix the key API being called on a host chosen at build time: a key's balance, its token signing and the keys created from those tokens now go to the MetaGer instance the key came from
- Fix search settings cookies not being cleared on instances beyond metager.de and metager.org
- Fix the MetaGer key being attached to searches whose query merely contained the word "keys" or "membership", which authorized those searches with the key instead of an anonymous token
- Fix search settings not being taken over from existing browser cookies when the extension is installed
- Fix a search setting whose value contains "%" or "=" being stored wrong, and one such setting discarding every other setting in the same response
- Fix the MetaGer key being deleted when a token refill spent the last of its charge
- Fix the logout link on the keyserver pages not being picked up on metager.de
- Fix anonymous token being counted as unspent if the browser stopped the extension mid-request
- Fix the request rules failing to install on a fresh Chromium profile ("Rule with id 3 does not have a unique ID."), which left searches without their settings, key or anonymous token headers
- Prepare for further MetaGer instances: host permissions covering a whole subdomain no longer break the request rules
- Add a test suite covering cookie handling in Chromium, Firefox and Firefox with First-Party Isolation
- Update all dependencies, drop the unused uuid package, and move the build to nodejs 22