Skip to main content

Biweekly Report (Jun 16 - Jun 30)

· 3 min read

From Jun 16th to Jun 30th, 29 contributors submitted 98 commits for Apache APISIX. Thank you all for your contributions to Apache APISIX. It is your selfless contribution to make the Apache APISIX project better!


Apache APISIX has grown as a community from the first day of open source and has quickly become the most active open source API gateway project in the world. These achievements cannot be achieved without the joint efforts of our community partners.

"If you want to go fast, go alone.If you want to go far, go together." The Apache APISIX Community Weekly Report hopes to help community members better understand the weekly progress of the Apache APISIX community and and facilitate everyone to participate in the Apache APISIX community.

We have also compiled some issues suitable for newcomers to the community to participate in! If you are interested, don't miss it!

Contributor Statistics

Contributors List
Click to Preview

New Contributors
Click to Preview

Good first issue

Issue #1075


Description: Currently, we will use the latest version of APISIX for e2e testing to ensure the compatibility of APISIX Ingress and APISIX.

But we don't know about some of the latest changes in APISIX. I suggest we add a scheduled job to use apisix:dev image for regression testing.

We used to use apisix:dev for e2e testing by default, but this way would affect our development experience, and sometimes we found that e2e failed, but it was actually just due to some changes in APISIX.

Highlights of Recent Features

Recent Blog Recommendations

This article mainly introduces how to write test cases for Apache APISIX API Gateway.

This article describes how Apache APISIX integrates with Ory Hydra to implement centralized authentication.

This article describes how Apache APISIX integrates with Keycloak (OpenID Connect Provider) to secure your APIs.

The Apache APISIX project website and the Github issue have accumulated a wealth of documentation and experience, so if you encounter problems, you can read the documentation, search the issue with keywords, or participate in the discussion on the issue to put forward your own ideas and practical experience.