Good day, charmers, Juju users and enthusiasts! The Juju team is happy to start providing regular updates about what is happening in Juju development 
.
Here is today’s agenda:
- Charm handling gets a serious upgrade
- Enhanced resource management and security improvements
- Stability fixes for cloud provider integrations
- Upcoming long-term support release promises new capabilities
- Juju 3.6, 3.6.1 releases
The Juju team continues the migration logic for storing, validating, and deploying charms to the Dqlite database. Recent changes removed redundant state calls, reduced complexity in packaging and uploading, and introduced a more direct pathway for handling charm versions. Meanwhile, service verification steps ensure that only well-validated charm configurations proceed, reinforcing stability at every stage.
Developers integrated a new resource service tightly with multiple system components, paving the way for consistent and straightforward resource handling. This move allows Juju to operate with resources (from binaries to container metadata) in the Dqlite database.
Alongside these technical advancements, new documentation efforts highlight secure product usage and cryptographic guidelines, ensuring that everyone, from seasoned admins to new users, can confidently adopt best practices.
Link: https://juju.is/docs/juju/security-with-juju
Changes to familiar commands like juju refresh offer more intuitive options, letting teams define bases and apply force-flags more transparently.
The team delivered a flurry of stability improvements targeting file handle leaks, login issues after model migrations, and cloud integration hiccups (notably within certain providers). Network configurations and database behaviors have also been fine-tuned.
The 3.6 LTS release is arrived. Rootless charms on Kubernetes promise more secure deployments, while Azure Managed Identities simplify interactions with cloud services. Idempotent secret management will introduce a better level of consistency for sensitive information handling. Interested parties can explore what’s ahead or share feedback, contributing to a more robust and user-friendly ecosystem.
Following the 3.6 release, the 3.6.1 update arrived, delivering a host of improvements and refinements. The platform now benefits from an upgraded Pebble version, preventing accidental controller replacements during registration (juju register), and removing reliance on specific upgrade-step APIs for migrations. In addition, the release resolves multiple issues—from handling controller outages and allowing charm pivots with juju refresh --base to eliminating bootstrap quirks on Kubernetes and addressing Azure integration errors. Notably, this update also optimizes the foundational txnwatcher to reduce the amount of data pulled from Mongo’s change-stream queries, preventing oversized documents and improving performance in complex deployments. Together, these enhancements further refine the overall performance of Juju’s evolving ecosystem.
For more details, head to:
Stay Tuned for More Juju Updates!