[repo-status] Weekly repository status — 16–23 August 2026

[github-actions]

Weekly status: 16–23 August 2026 🌟

CloudStack had a productive week focused on security, release readiness, and operational reliability.

Highlights

• Security and releases: Apache CloudStack 4.22.1.1 and 4.20.3.1 shipped on 21 August as LTS security releases. They address a broad set of reported security issues across command injection, SSRF/RCE, access control, OAuth/LDAP, webhook handling, information disclosure, XSS, and SAML validation. Maintainers and operators should prioritize reviewing the advisory and upgrading supported installations.
• Code delivery: 21 commits landed on main, including backup-service API typing, quota/usage corrections, API key-pair restructuring follow-ups, KBOSS and NAS/LINSTOR backup fixes, backup repository mount handling, and forward-merge/build maintenance.
• Issue flow: 82 issue records were updated during the week. Active topics include Kubernetes Metric API availability, VPC/router health-check behavior, VMware and Ceph import/migration paths, usage duplication and snapshot attribution, LDAP/Keycloak configuration, ConfigDrive, and Web UI resource-limit and account-deletion flows.
• Collaboration: Recent delivery was coordinated through pull-request-linked changes including #13940, #13936, #13828, #13880, #13896, #13909, and #13538.

Project status

The project is moving well: security response and LTS maintenance are demonstrably active, while ongoing fixes continue to improve backup, usage accounting, API correctness, and infrastructure integrations. The volume and breadth of open issue activity also indicate a healthy queue for triage and contributor engagement.

Recommended next steps

1. Prioritize upgrades to 4.22.1.1 or 4.20.3.1 where applicable, and communicate the security advisory to operators.
2. Triage the newest operational regressions first—especially usage duplication, VPC gateway health checks, VMware/Ceph migration, Kubernetes metrics, and backup restore compatibility.
3. Close the loop on release follow-ups: verify forward-merge/build stability, add regression coverage for the recent quota, usage, backup, and API fixes, and keep documentation aligned with the security releases.
4. Keep contributor momentum high by reviewing the recent PR-linked changes and labeling/routing the growing UI, networking, storage, and identity queues.

Thanks to everyone who contributed reviews, fixes, releases, and issue reports this week! 🚀

Generated by Weekly Repo Status · gpt56 232.1K · ◷

Add this agentic workflows to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-status.md@main