github-actions[bot] opened a new issue, #14382:
URL: https://github.com/apache/cloudstack/issues/14382

   ## Apache CloudStack weekly status ๐ŸŒŸ
   
   **Reporting period:** 2026-10-04 through 2026-10-11
   
   CloudStack continues to move forward with strong delivery across platform 
features, networking, dependency maintenance, and CI reliability.
   
   ### Highlights
   
   - **Feature delivery:** [Instance boot groups and readiness 
rules](https://github.com/apache/cloudstack/pull/13907) merged on Oct 8. This 
is a substantial cross-cutting feature spanning API, KVM, virtual-router, UI, 
and integration coverage, with an upgrade path toward 4.24.
   - **Networking:** [BGP route-maps for routed-mode virtual 
routers](https://github.com/apache/cloudstack/pull/9964) merged on Oct 7, 
tightening route advertisement and acceptance boundaries for newer FRR versions.
   - **Dependency health:** [Netris SDK 
1.1.0](https://github.com/apache/cloudstack/pull/14365) merged on Oct 9, 
addressing the current Bouncy Castle compatibility path.
   - **CI and project hygiene:** [docker/login-action was 
upgraded](https://github.com/apache/cloudstack/pull/14276) to resolve an ASF 
Allowlist failure, and a pre-commit validation hook for `dependabot.yml` landed.
   - **Active improvement:** [Dynamic `vpc.max.networks` 
handling](https://github.com/apache/cloudstack/pull/14373) is open, improving 
runtime configurability and returning a clear HTTP 431 limit response with unit 
and simulator coverage.
   - **User-reported follow-up:** [Issue 
`#14381`](https://github.com/apache/cloudstack/issues/14381) reports a 
misleading canceled-request notification when switching from a project to the 
default view on the Instances page in 4.20.3.1.
   
   ### Release and project status
   
   The latest regular release remains 
[4.23.0.0](https://github.com/apache/cloudstack/releases/tag/4.23.0.0), 
published Sep 2. The latest maintenance/security releases are 
[4.22.1.1](https://github.com/apache/cloudstack/releases/tag/4.22.1.1) and 
[4.20.3.1](https://github.com/apache/cloudstack/releases/tag/4.20.3.1), 
published Aug 21. Current main-branch work is aligned with the 24.0 milestone 
and continues to build toward the next release line.
   
   ### Recommended next steps
   
   1. Complete review and validation of `#14373`, especially configuration 
refresh behavior and compatibility for existing deployments.
   2. Triage `#14381` against the 4.20.3.x maintenance branch and suppress only 
deliberately canceled UI requests, while preserving genuine network-error 
reporting.
   3. Keep the 24.0 release train moving by prioritizing integration/regression 
coverage for the new readiness-rule feature and networking changes.
   4. Continue dependency and CI action maintenance, and keep the 
4.23/4.22/4.20 documentation and upgrade guidance synchronized with supported 
release branches.
   
   Thanks to everyone contributing code, reviews, testing, documentation, and 
release support! ๐Ÿ™Œ
   
   
   
   
   > Generated by [Weekly Repo 
Status](https://github.com/apache/cloudstack/actions/runs/38139149221) ยท gpt56 
169K ยท 
[โ—ท](https://github.com/search?q=repo%3Aapache%2Fcloudstack+is%3Aissue+%22gh-aw-workflow-call-id%3A+apache%2Fcloudstack%2Fweekly-repo-status%22&type=issues)
   >
   <details>
   <summary>Add this agentic workflows to your repo</summary>
   
   To install this agentic workflow, run
   
   ```
   gh aw add githubnext/agentics/workflows/repo-status.md@main
   ```
   </details>
   
   
   <!-- gh-aw-agentic-workflow: Weekly Repo Status, engine: copilot, version: 
1.0.52, model: gpt-5.6-luna, id: 38139149221, workflow_id: weekly-repo-status, 
run: https://github.com/apache/cloudstack/actions/runs/38139149221 -->
   
   <!-- gh-aw-workflow-id: weekly-repo-status -->
   <!-- gh-aw-workflow-call-id: apache/cloudstack/weekly-repo-status -->


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to