Repository navigation
1.5.1
1.5.1
For a server running v1.5.0, this is a maintenance release with no change to how mailboxes, commands, permissions or configuration work. It updates the bundled usage-reporting client and points the usage-reporting details link at a new page. Usage reporting sends the same data, follows the same opt-outs and keeps the same server ID. No PR numbers were recorded for this release.
Changes
Usage reporting
- The link to usage-reporting details now points to https://danielstephenson.dev/usage-reporting. This affects the startup console message, the comment in a newly generated
config.ymland the comment in a newly createdplugins/trace/config.yml. Existing config files are not rewritten. - The bundled trace client is updated from 0.5.0 to 0.6.1. Mailboxes keeps using the server-wide
server-idinplugins/trace/config.yml, and every opt-out works as before:usage-reporting.enabled: false,enabled: falseinplugins/trace/config.yml,TRACE_USAGE_REPORTING=offandDO_NOT_TRACK=1.
Version
v1.5.0 → 1.5.1 — PATCH. Mechanical floor from comparing the two jars: PATCH.
Judgment: The only API additions are in the bundled trace client: TraceClient.installIdFromFile(File) and Builder.installIdFile(File). Mailboxes calls neither, so the plugin keeps resolving its install ID from server-id in plugins/trace/config.yml exactly as before. Everything else just changes the usage-reporting details link in the console message, the default config.yml comment and the comment in a newly generated plugins/trace/config.yml. Commands, permissions, config keys and stored mailbox data are untouched, so the patch floor stands.
- no interface or storage difference observed between the jars
Java API changes (informational — nothing depends on this plugin)
- dansplugins.mailboxes.trace.TraceClient: added public static java.lang.String installIdFromFile(java.io.File);
- dansplugins.mailboxes.trace.TraceClient$Builder: added public dansplugins.mailboxes.trace.TraceClient$Builder installIdFile(java.io.File);
Verification
Verified on a real Spigot server before publication; this release carries the exact jar that was verified.
- boot gate run: booted twice on a fresh Spigot server running Minecraft 1.19.4 (11 assertions passed).
- boot gate run: booted twice on a fresh Spigot server running Minecraft 1.21.11 (11 assertions passed).
- boot gate run: booted twice on a fresh Spigot server running Minecraft 26.2 (11 assertions passed).
- boot gate run: booted twice on a fresh Spigot server running Minecraft 26.3 (11 assertions passed).
- save-compatibility gate run: data written by
v1.5.0was loaded by this release across two restarts with nothing lost (16 assertions passed).
Install with Dan's Plugin Manager: /dpm get <plugin>. How stable releases are made: Release channels.
drafted by Claude on behalf of Daniel Stephenson