[repo-status] Weekly Repository Status - Week of February 17-23, 2026 🚀

[github-actions]

Hello team! Here's your weekly status update for rebar3_gpb_plugin 🌟

🎉 This Week's Highlights

Workflow Optimization Success ✅

• Successfully transitioned from daily to weekly status reports (PR Change repo status report from daily to weekly schedule #183 merged Feb 15)
• Cleaner notifications and better maintainer experience
• Automated reporting now runs every Monday at 18:00 UTC

Latest Release - Version 2.23.8 🆕

• Updated to gpb 4.21.7 (Feb 15, 2026)
• Two consecutive releases shipped (2.23.7 and 2.23.8)
• Demonstrates strong project maintenance and dependency management

📊 Repository Health Check

Community Metrics:

• ⭐ 55 stars | 🔀 36 forks
• 📝 11 open issues | 🔧 2 open pull requests
• 🏷️ Latest version: 2.23.8
• 💻 Primary language: Erlang
• 📄 License: MIT

Activity Level: Healthy - Active maintenance with regular updates

🔍 Issues Requiring Attention

Critical Priority

#176 - Plugin clean fails (March 2025)

• rebar3 protobuf clean not removing proto output files correctly
• Fix available in PR Fix clean problem and tidy up #172 - Strong candidate for review!
• Community contributor waiting for feedback

#116 - Circular dependencies cause infinite loop (2020)

• Proto files with circular dependencies trigger endless compilation
• Needs dependency tracking enhancement
• Long-standing reliability issue

Configuration & Usability

#156 - Umbrella project path generalization (2022)

• Users requesting better path handling for multi-app projects
• Related to closed issue umbrella not supported #167
• Documentation improvements could help

#147 - Version 2.20.2 compatibility issue (2021)

• gpb_compile:list_io function undefined error
• Known workaround: Use version 2.20.1
• May need version compatibility documentation

Feature Requests

#114 - GRPC support (2020, 4 comments)

• Community interest in gRPC protobuf support
• Worth evaluating feasibility and demand

🔧 Pull Requests Status

Awaiting Review - HIGH PRIORITY

PR #172 - Fix clean problem and tidy up (March 2024, updated Jan 2025)

• ⚠️ Nearly 2 years old - needs urgent attention
• Directly addresses issue plugin clean proto output files failed. #176 (clean functionality)
• Includes code tidying and verbose argument improvements
• Community contributor @haoxianhan has been patient
• Action needed: Review and merge or provide feedback

PR #163 - Support o_nif_cc gpb option (February 2023)

• ⚠️ 3 years old
• Adds NIF C++ compilation support
• Bumps gpb to latest version
• Action needed: Evaluate for merge or close with explanation

💡 Recommendations for Maintainers

Immediate Actions (This Week)

1. Review PR Fix clean problem and tidy up #172 🎯

   • Longest pending PR with direct bug fix
   • Community goodwill at stake
   • Could close issue plugin clean proto output files failed. #176 simultaneously

2. Decision on PR [support-o_nif_cc] Support o_nif_cc gpb_opt #163

   • Evaluate NIF C++ support feature
   • Merge or close with clear rationale

Housekeeping (Next 2 Weeks)

3. Triage stale issues

   • Request updates on issues from 2019-2021:
     • Regeneration of file if already in place? #89 (2019) - Regeneration of file if already in place
     • compile proto error in LAN #97 (2019) - Compile proto error in LAN
     • Is it possible to overwrite dependency fetching with local git repo path #142 (2021) - Local git repo path overwriting
     • Issue with latest rebar3 #143 (2021) - Issue with latest rebar3
   • Consider closing if no longer relevant

4. Documentation enhancements

   • Add troubleshooting section
   • Umbrella project configuration guide (how to generalize the proto files path for umbrella projects #156)
   • Version compatibility matrix (Issu with rebar3 and last version of gpb plugin #147)
   • Common error resolution patterns

Long-term Planning

5. Feature roadmap

   • Evaluate gRPC support demand (Can you support GRPC protobuf? #114)
   • Community survey for priority features
   • Consider creating a ROADMAP.md

6. Release management

   • Create CHANGELOG.md for better version tracking
   • Document breaking changes clearly

🎯 Actionable Next Steps

This week's focus:

• Review and provide feedback on PR Fix clean problem and tidy up #172
• Make decision on PR [support-o_nif_cc] Support o_nif_cc gpb_opt #163 (merge or close)
• Update documentation for umbrella projects
• Request updates on 3+ year old issues

Next week:

• Create troubleshooting documentation
• Consider version compatibility guide
• Evaluate community feature priorities

🌟 Overall Project Status: Healthy ✅

Strengths:

• ✅ Excellent dependency management (quick gpb updates)
• ✅ Regular releases and active maintenance
• ✅ Clear MIT license and good documentation
• ✅ Strong community engagement (55 stars)
• ✅ Automated workflow improvements

Opportunities:

• ⚠️ Two long-standing PRs need resolution
• ⚠️ Some legacy issues could use triage
• 💪 Documentation could be expanded
• 💪 Issue closure rate could improve

---

Fantastic work maintaining this essential Erlang protobuf tooling! 🎊

The project shows excellent stewardship with rapid dependency updates and consistent releases. A focused PR review session and documentation update would significantly enhance the repository's health and community satisfaction.

This report was automatically generated by the weekly repo-status workflow

---

Generated by Weekly Repo Status Workflow

Reporting period: February 17-23, 2026

Generated by Weekly Repo Status

To install this workflow, run gh aw add githubnext/agentics/workflows/daily-repo-status.md@eb7950f37d350af6fa09d19827c4883e72947221. View source at https://github.com/githubnext/agentics/tree/eb7950f37d350af6fa09d19827c4883e72947221/workflows/daily-repo-status.md.