Skip to content

2.2.1

Latest

Choose a tag to compare

@dmccoystephenson dmccoystephenson released this 07 Oct 02:17
f9c963e

2.2.1

This is a maintenance release for servers running v2.2.0. Messaging, commands, permissions, configuration and stored data all work as before, and usage reporting behaves exactly as it did, including the server-wide opt-out and the existing server-id. The only thing an operator will notice is a new link for the usage-reporting details.

Changes

Usage reporting

  • The usage-reporting details link now points to https://danielstephenson.dev/usage-reporting. You will see it in the startup console message, in the default config.yml comments and in the comment header of a newly created plugins/trace/config.yml. Existing config files are not rewritten.
  • The bundled usage-reporting client is updated to 0.6.1. Herald's reporting behaviour is unchanged: the same opt-outs apply, and a disabled client still reads and writes nothing.

Version

v2.2.0 → 2.2.1 — PATCH. Mechanical floor from comparing the two jars: PATCH.
Judgment: Herald itself behaves the same as in v2.2.0. The bundled usage-reporting client moves from 0.5.0 to 0.6.1. Its new installIdFile/installIdFromFile API is meant for non-Spigot programs, and Herald never calls it, so the install ID still comes from server-id in plugins/trace/config.yml. The only other changes are the usage-reporting details link in the console message, in config.yml comments and in the comment header of a newly created plugins/trace/config.yml, so I kept the patch floor. No merged pull requests were recorded, so the notes cite no PR numbers.

  • no interface or storage difference observed between the jars
Java API changes (informational — nothing depends on this plugin)
  • com.dansplugins.herald.trace.TraceClient: added public static java.lang.String installIdFromFile(java.io.File);
  • com.dansplugins.herald.trace.TraceClient$Builder: added public com.dansplugins.herald.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).

Install with Dan's Plugin Manager: /dpm get <plugin>. How stable releases are made: Release channels.


drafted by Claude on behalf of Daniel Stephenson