Charm Tech pulse 2026#17

charm
1

This pulse Charm Tech is back in full swing, ready for the second half of the cycle. We are very close to the 1.0 release of Hyrum, and an alpha release of the new charmlint tool. We finalised the migration of charms.tempo_coordinator_k8s.v0.tracing to Charmlibs. We began prototyping work on OTLP enrichment proxy in Pebble. And a full Concierge documentation site is on the way!

Jubilant’s wait method can now be used from the CLI. This feature will be part of the next Jubilant release, so keep an eye out for it.

Ops

  • Fixed a crash that could occur if tests try to create an unknown status with a message (#2700).
  • Continued work on OP089 - Multiple-charm state transition tests.

Charming

  • In Hyrum: fixed patching ops to a PyPI version emitting a single comparison operator (#123) and made --limit count the charms that actually run rather than the ones it looked at (#124).
  • In the Ubuntu charm: scoped the publish job to the charmhub-edge environment (#113), adopted the charm-ci release toggles (#114), and then moved the charm-ci pins to v1.0.0 (#115).
  • Continued work on the new charmlint tool. We’re hoping there will be an alpha release next week.
  • Added a CLI entrypoint that exposes Jubilant’s wait method (#374).
  • Continued work on modernising the Juju controller charm.
  • Began work on updating jhack scenario snapshot.
  • Worked on improving Ops CI for running example charm integration tests (#2655, #2696).

Charmlibs

  • Documented that new libraries can no longer be published to Charmhub, and that updating existing libraries will be disabled next cycle (#644).
  • Worked on a stub implementation for charmcraft create-lib so failure doesn’t require a store round-trip (#2581).
  • Made charmlibs.snap 2.0 error attributes private, in preparation for the 2.0 release next pulse (#622).
  • Worked on stopping the rollingops etcd integration tests racing the worker poll loop (#640).
  • Worked on migrating the tracing library from tempo-coordinator-k8s (#588).
  • Pinned the interface testing workflow in preparation for changing how we store interface metadata and dropping interface testing (#645).
  • Fixed non-leader databag reading of TLS Certificates in hybrid app+unit databag mode (#641).
  • Enabled warnings-as-errors in Charm Tech owned libraries and provided scaffolding for customising pytest config per library (#612, #639).
  • Fixed publication issues stemming from a Hatch/Twine version release and mismatch (#634, #635, #636).
  • Added top-level entry points to library migration docs to agent documentation (#633).

Pebble

  • Cont. prototyping on OP092 - Pebble scheduled service start (#917).
  • Cont. prototyping on OP090 - Pebble TLS trust context (#918).
  • Prototyping on OP091 - Pebble OTLP enrichment proxy (#919).
  • Automate more of the Pebble release process.

Documentation

  • Changed the guidance to recommend spread directly rather than charmcraft test (#2706).
  • Extracted sections in how to write integration tests to their own howto guide (#2662).
  • Continued work on a full Concierge documentation site, which will come to ubuntu.com/juju/docs some time in the future (#248).
1 Like