Patch release. One observable change, and it only reaches deployments that run with continuous profiling switched on. Everything else is documentation and docs-site dependency updates. No configuration, schema or data migration.
If you run with profiling enabled
Riptide now ships Pyroscope agent 2.9.2, where v0.13.0 shipped 2.9.1. The agent vendors protobuf 4.36.1 instead of 4.33.5, and no longer touches sun.misc.Unsafe when it encodes a profile, so this warning stops appearing:
WARNING: sun.misc.Unsafe::arrayBaseOffset has been called by io.pyroscope.vendor.com.google.protobuf.UnsafeUtil$MemoryAccessor
Is this you? Only if profiling is on — RIPTIDE_PROFILING_ENABLED=true in the environment file, or riptide.profiling.enabled: true in the config. To confirm you were seeing it:
journalctl -u riptide | grep 'sun.misc.Unsafe::arrayBaseOffset'What to run: nothing beyond the upgrade itself. If you added --sun-misc-unsafe-memory-access=allow to JAVA_OPTS purely to silence that warning, you can drop it now. It only ever deferred the problem, and it deferred it badly: when the JDK removes the option, an unrecognised flag stops the JVM from starting at all.
How far this was checked. Measured on one JVM (openjdk 25.0.4) with 2.9.1 as a control: each version started the agent against a local server that accepted four uploaded profiles, so the encode path ran in both. 2.9.1 emitted the warning; 2.9.2 emitted no line mentioning Unsafe at all. That is a local probe, not a fleet. The call still exists in the vendored class and still warns if something forces it to initialise — what changed is that the agent's own path no longer does. If you see a UnsafeUtil line on 2.9.2, that is a path the probe never reached: please open an issue.
The other profiling warning is unrelated and unchanged. It comes from the agent loading a native library, and it still wants --enable-native-access=ALL-UNNAMED.
If you do not run profiling
Nothing in this release reaches you. Upgrade at your convenience.
Also in this release
Documentation: the operations page now records that the sun.misc.Unsafe warning is gone as of agent 2.9.2, and pairs --enable-native-access with the profiling switch rather than leaving the two to be connected by the reader (#785, #792).
Five docs-site dependency updates (#786–#790). These affect the documentation build only and are not part of any shipped artifact.