2.15.0 Support Pebble check-failed and check-recovered events

What's Changed

This release adds support for new events based on Pebble checks. As of Juju 3.6b2, when a Pebble check reaches the failure threshold, a PebbleCheckFailedEvent will be emitted - and when the check starts passing again, the charm will get a PebbleCheckRecoveredEvent. Kubernetes charms can observe these events to react to failing checks - for example, change the unit or application status, output additional logging, or dynamically adjust the workload to work around the failure.

• Add support for Pebble check-failed and check-recovered events in #1281

Fixes

• Pass secret data to Juju via files, rather than as command-line values in #1290 fixing CVE-2024-41129
• Include checks and log targets when merging layers in ops.testing by @amandahla in #1268

Documentation

• Clarify distinction between maintenance and waiting status in #1148

CI

• Bump the Go version to match Pebble in #1285
• Run ruff format over charm pin update code in #1278
• Bump certifi from 2024.2.2 to 2024.7.4 in /docs in #1282
• Update charm pins in #1269

New Contributors

• @amandahla made their first code contribution in #1268

Full Changelog: 2.14.1...2.15.0