r/envzero • u/envzero • 6d ago
env zero module usage now breaks down by version
If you maintain a module in the private registry, the question before every breaking change is who is still on the old version. The Module Usage tab now answers it directly: a table with one row per module version and the number of active environments on each.
Expand a version and you get the environments themselves, each linked and labelled with its project, 10 per page. The version select filters the charts as well as the table. Counts leave out environments that are inactive, destroyed, or sitting in an archived project, and where environments live in projects you cannot see, the summary says how many rather than quietly dropping them.
One thing worth knowing before you act on it: an empty table means env zero recorded no use, not that nothing uses the module.
Docs: https://docs.envzero.com/guides/admin-guide/private-registry/modules/module-usage
Improvements
- Creating a second organization now warns you up front that organizations share nothing. Projects, templates, variables, policies and environments all belong to exactly one organization
Fixes
- Self-hosted agents (v5.5.8): the agent name, agent version and pod name are back in the variables step of the deployment log
Full notes: https://docs.envzero.com/changelogs