Ops 3.8.3 fixes a security issue GHSA-4356-5g33-3qrp.
Starting in Ops 3.4.0, charms with tracing enabled and with an integration with a tracing receiver would send Juju secret content to their tracing receiver. Anyone with access to the trace data, such as Tempo, could read it.
Ops 3.8.3 no longer records these values in traces. It also removes the action-set and action-log command line arguments out of HookError, so those won’t appear in tracebacks in the debug log (in case those contain sensitive information).
If your charm uses ops[tracing] and you’re on Ops 3.x, update to Ops 3.8.3 and release a new revision. 3.8.3 contains no changes other than these two security fixes, compared to 3.8.2. A normal update with other improvements is expected next week.
Charms without tracing aren’t affected. Consider asking your users to rotate any secrets that might already be in their trace data.