[renvins]

Summary

This PR updates ServerPulse to 0.5.5-SNAPSHOT, improves metrics sending reliability and safety, cleans up a few API/implementation details, and introduces a CI workflow to automatically create GitHub releases when the Gradle version changes.

Changes

• Versioning

  • Bump root project version from 0.5.2-SNAPSHOT to 0.5.5-SNAPSHOT in build.gradle.kts.
  • Update Velocity plugin metadata to 0.5.5-SNAPSHOT to keep it in sync.

• Metrics & database behavior

  • MetricsService: send line protocol asynchronously and log an error when InfluxDB reports a failure instead of assuming success.
  • DatabaseService:
    • Make startRetryTaskIfNeeded a private helper instead of part of the public IDatabaseService API.
    • Minor cleanup of retry logic (remove stray extra semicolon).

• API / data model

  • AsyncMetricsSnapshot:
    • Fix spelling from commitedHeap → committedHeap (field, constructor parameter, getter).
  • LineProtocolFormatter:
    • Use the corrected getCommittedHeap() when writing the available_memory field, ensuring the metric name and accessor are consistent.
  • IDatabaseService:
    • Remove the startRetryTaskIfNeeded() method from the public interface (now internal to DatabaseService).

• Utility

  • ChatUtils:
    • Make format null-safe by returning an empty string when the input message is null instead of throwing a NullPointerException.

• CI / Releases

  • Add .github/workflows/auto_release_on_version_change.yml:
    • Triggers on push to master when build.gradle.kts changes.
    • Compares the current version to the previous commit’s version.
    • If the version changed, automatically creates a GitHub release with:
      • Tag and name: v<version>
      • Body generated from the commits between the previous tag (if any) and HEAD.
    • Integrates with the existing Create Release Assets workflow that attaches built JARs to the release.

Potential impact / breaking changes

• Removing startRetryTaskIfNeeded() from IDatabaseService is a source-breaking change for any external consumers that used that method; it remains available as a private implementation detail in DatabaseService.
• The heap metric naming change is a behavioral fix; dashboards depending on the value should see consistent data, but the field name itself (available_memory) is unchanged.