[repo-status] Weekly Repo Status - February 13, 2026

[github-actions[bot]]

Hey kongctl community! 👋 Here's what's been happening this week in the project.

🎉 Highlights

Version 0.4.1 Released! 🚀
The team shipped a critical authentication fix this week that corrects token expiry and refresh URL handling in the auth flow. This ensures more reliable long-running operations.

All 7 Core Development Stages Complete! ✅
The declarative configuration feature set has reached full implementation across all planned stages - from basic CLI to namespace-based resource management. This is a major milestone for the project!

📊 Activity Summary

Recent Releases

• v0.4.1 (Feb 13) - Auth flow improvements
• v0.4.0 Beta (Feb 10) - Major feature release with Kong branding updates and extended resource support

Merged Pull Requests (Last 7 Days)

• Task: Changes the AW for repo status to weekly #376 - Task automation improvements (weekly repo status)
• Add agentic workflow daily-repo-status #373 - Added agentic workflow for daily repo status
• Release: 0.4.1 #372 - Release 0.4.1 with auth fixes
• Fix: Correct token expiry and refresh URL in auth flow #371 - ⭐ Critical fix: Token expiry and refresh URL correction
• Feat: Kong branding update to color theme #368 - Kong branding update to color theme
• Feat: Extends supported resources for kongctl view #351 - Extended supported resources for kongctl view
• fix: hide event gateway behind flag #367 - Disabled event gateways by default until full implementation
• Fix: Makes declarative dump command work with child resources #363 - Fixed declarative dump command for child resources

Active Development

• chore(deps): update actions/download-artifact action to v7 #374 - Dependency update for download-artifact action (open PR)
• Feat: Event Gateway Listeners #365 - Event Gateway Listeners feature (in progress)

🐛 Known Issues & Bugs

The team has identified several important issues that need attention:

High Priority:

• Bug: Access token not refreshed during long-running operations; mid-flight 401 causes partial failures #370 - Access token not refreshed during long-running operations, causing mid-flight 401 failures. This affects large declarative configurations that take >15 minutes to apply.
• Bug: An empty config.yaml file alters the behavior of config loading and auth resolution #362 - Empty config.yaml file unexpectedly alters auth resolution behavior
• Bug: diff command does not accept mode #361 - diff command missing mode parameter support

📋 Planning Status

All 7 planned development stages are 100% complete:

1. ✅ Configuration Format & Basic CLI
2. ✅ Plan Generation with Label Management
3. ✅ Plan Execution
4. ✅ API Resources and Multi-Resource Support
5. ✅ Sync Command Implementation
6. ✅ Namespace-Based Resource Management
7. ✅ Testing, Documentation, and Core Improvements

The project now has a complete declarative configuration management system with support for Portals, APIs, child resources, and namespace isolation.

🎯 Feature Roadmap

Open Feature Requests (67 total issues):

• Event Gateway support (Feat: Event Gateway Support #196, Feat: Event Gateway Listeners resource support #212, Feat: Event Gateway DataPlane Certificates resource support #217, Feat: Event Gateway Static Keys resource support #218)
• Service Catalog Integration (Feat: Service Catalog Integration Instance resource support #221, Feat: Service Catalog Integration Instance Auth Credential resource support #222, Feat: Service Catalog Integration Instance Auth Config resource support #223)
• Identity & Organization management (Feat: Organization support #257-Feat: Auth settings resource support #267)
• System account access tokens (Feat: System account access token resource support #259)
• And many more...

💡 What's Next?

For Maintainers:

1. Address critical auth issue Bug: Access token not refreshed during long-running operations; mid-flight 401 causes partial failures #370 - Token refresh during long operations is important for production use
2. Review open PRs - chore(deps): update actions/download-artifact action to v7 #374 (dependency update) and Feat: Event Gateway Listeners #365 (Event Gateway Listeners)
3. Triage bug reports - Bug: diff command does not accept mode #361 and Bug: An empty config.yaml file alters the behavior of config loading and auth resolution #362 need investigation
4. Consider roadmap priorities - With core features complete, evaluate which of the 67+ open feature requests should be prioritized

For Contributors:

• Check out the comprehensive planning documentation to understand the project structure
• The codebase follows clear patterns - see CLAUDE.md for development guidelines
• Integration test infrastructure is ready for new features

📈 Project Health

Good:

• ✅ Consistent release cadence
• ✅ Strong architectural foundation with completed core features
• ✅ Comprehensive planning and documentation
• ✅ Active bug fixing and improvements

Needs Attention:

• ⚠️ Growing issue backlog (67 open issues)
• ⚠️ Authentication reliability for long-running operations
• ⚠️ Feature prioritization needed now that core work is complete

🙌 Community

This week saw 8 merged PRs and continued progress on the Event Gateway feature. The development momentum is strong!

Remember: kongctl is Beta software - not recommended for production use yet, but getting closer every day!

---

Have questions or suggestions? Drop a comment below! 💬

AI generated by Weekly Repo Status

• expires on Feb 20, 2026, 10:20 PM UTC