Yilialinn opened a new pull request, #2092:
URL: https://github.com/apache/apisix-website/pull/2092

   ## Summary
   
   Correct the contributor statistics in the July 2026 community monthly report 
(EN + ZH) so they use the requested `apache/apisix` default-branch commit scope.
   
   The previously published contributor images reflected the old aggregation. 
This change replaces them with explicit placeholders until matching formal 
images are available; the existing English and Chinese cover images remain 
unchanged.
   
   ## Data Snapshot
   
   - Target month: July 2026
   - Repository and branch: `apache/apisix` `master` (default branch)
   - Commit interval: `[2026-07-01T00:00:00Z, 2026-08-01T00:00:00Z)`
   - Snapshot captured: `2026-07-31T09:07:43Z`
   - First commit in the interval: `2f8178093f2c79040527bc76ccbe42394d4676bb`
   - Latest commit available in the interval at snapshot time: 
`906d883e6ef865f238d1911efca71ad5e8931d75`
   - Statistics: **15** contributors, **79** commits
   - Contributor logins: AlinsRan, YapWC, Yilialinn, cybersec-jochenarnold, 
ecsimsw, janiussyafiq, juzhiyuan, kayx23, luarx, moonming, nic-6443, 
prasunsrivastav123-lang, pronchakov, shreemaan-abhishek, suryaparua-official
   - New contributors: **6** — cybersec-jochenarnold, ecsimsw, luarx, 
prasunsrivastav123-lang, pronchakov, suryaparua-official
   
   New contributors were cross-checked against both default-branch commits and 
merged PRs before `2026-07-01T00:00:00Z`; each of the six accounts had neither.
   
   ## Feature Highlights Covered
   
   The feature set is unchanged from #2091 and still contains all 15 eligible 
feature PRs collected by the monthly-report automation.
   
   ### AI Gateway Caching, Routing, and Rate Limiting
   
   1. **Semantic L2 caching for `ai-cache`** - PR #13632
   2. **Streaming response caching with format tagging** - PR #13644
   3. **Redis-backed shared counters for `ai-rate-limiting`** - PR #13670
   4. **Semantic load balancing in `ai-proxy-multi`** - PR #13676
   
   ### AI Gateway Security and Observability
   
   5. **Prometheus metrics for AI cache performance** - PR #13659
   6. **Moderate System and Tool Content with `ai-aliyun-content-moderation`** 
- PR #13646
   7. **LLM response moderation with AWS Comprehend** - PR #13735
   
   ### Traffic Handling and Upstream Health
   
   8. **Encoded slash preservation in path parameters** - PR #13626
   9. **Preserve Client Addresses Across Stream PROXY Protocol Hops** - PR 
#13700
   10. **Multiple same-name headers in `proxy-rewrite`** - PR #13597
   11. **Custom methods and bodies for active health checks** - PR #13726
   
   ### Platform Reliability and Integrations
   
   12. **Increase Default Sizes for Non-Evictable Shared Dictionaries** - PR 
#13688
   13. **TLS support for Kafka logger plugins** - PR #13607
   
   ### Gateway Security and Identity
   
   14. **Bounded request and response body buffering** - PR #13705
   15. **Raw signed ID token forwarding in `openid-connect`** - PR #13616
   
   ## Good First Issue
   
   No open `good first issue` created or labeled in July was found, so the 
section remains omitted.
   
   ## Verification
   
   - `git diff --check`: passed
   - Markdownlint and frontmatter checks for both changed files: passed
   - Remark: Chinese report clean; English report has only three pre-existing 
heading-length warnings and no new warnings
   - English blog production build: passed
   - Chinese blog production build: stopped before content compilation by the 
repository's existing `readingTime` configuration validation error
   - Independent pre-PR review: completed; all actionable findings addressed
   
   ## TODO (Manual)
   
   - [ ] Replace `TODO_CONTRIBUTOR_LIST_IMAGE` with a contributor image 
matching the corrected 15-account snapshot
   - [ ] Replace `TODO_NEW_CONTRIBUTORS_IMAGE` with a new-contributor image 
matching the corrected six-account snapshot
   


-- 
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