Devlog and bug tracking for your tools, and the changelog by mail

This release is about the time after launch: the devlog where you tell people what changed, and the bugs your players report.

The devlog through the API

Devlog entries can now be created, changed, published and deleted through the API as well, drafts included. The new scope for that is write:devlog. The rules are the same as in the panel: publishing needs an English version, and a changed address redirects from the old one.

That lets you write the entry for a release where your code lives, for example with an AI assistant through the MCP adapter.

Working through bug reports

With the new scope manage:bugs, a tool reads the reported bugs: context, log, the player's note, versions and how often a bug happened. It marks them as reproduced, fixed or open again. The API never hands out a player's address.

The key your game uses to report stays as it was: it may report and nothing else.

Links in the header

As soon as your devlog has its first published entry, it appears in your site's header, in every language that has entries. The same goes for the public bug list once you switch it on. Nothing to link by hand.

The changelog by mail

What is new in willyoubuyit now arrives by mail if you want it. Switch it on in your account under Notifications. Every mail has a one-click unsubscribe.

Fixed

• Whoever opened the second page of your devlog first could leave it behind as the first page for everyone else. Later pages of a list are no longer cached.

Under the hood

• Laravel 12.69 and updated dependencies.
• The MCP adapter can read its token from a file, so it does not have to sit in the configuration.