Meshery Development Meeting | January 7th, 2026

Community
, ,
1

January 7th, 2026

Attendees:

  • Raunak Madan, Lee Calcote, Yash Sharma, Kavitha Karunakaran, Raja Rathour, Yash Mahakal
  • Parthiv Saikia,Shrikant Shingare, Aabid Sofi
  • Prachi Saran, Suhani, Hussaina Begum
  • Yelsin Sepulveda, Charan Naidu, Cyril Baah,APIPAWE KATOTO Daniel,
  • Matthieu Evrin, Harsh Singh

Announcements:

  • The first Meshery Dev meeting of the year!!
  • Updated Meshery Playground sandbox cluster.
    • Note: Deploy test designs to the playground-sandbox namespace.

Topics:

Release in-progress: v0.9.0 GitHub Milestone

  • [Lee Calcote] v.0.9.0 release readiness? Over a year since v0.8.0 was released on Dec 20, 2024
  • [Yash Sharma] Timing and hosting of Newcomers meeting
  • [Parthiv Saikia] mesheryctl registry generate -–check PR
  • [Lee Calcote] Overhaul of mesheryctl registry generate PR #16863
  • [Aabid Sofi]
    • Mark these tests accordingly, if they are not ready to be enforced.
    • Centralized reporting of tests for meshery and its extensions at qa.meshery.io
    • Add support for reporting mesheryctl e2e tests
  • [Lee Calcote] Current quality of relationship definitions?
    • How are relationships validated during development?
  • [Lee Calcote] Is feasibility analysis of relationships or of Meshery Server being greedy?
  • [Raunak Madan] Skip auto commit for fork based PRs in Rego Lint and Test Workflow #16864
  • [Raja Rathour] As a newbie how should we contribute in Meshery, I have my first PR #16841
  • [APIPAWE KATOTO Daniel] - Fix related blogs slider responsiveness #7323 link
  • [Yelsin S.] ’’mesheryctl’ Refactor: Replace logrus with meshkit logger PR #16819
    • New helper functions added to ’meshkit’ PR #888
  • [Harsh Singh] Discussion on PR #16843 – Cleanup of unused deny selector logic in Rego policies

Backlog:

  • [Harsh Singh] PR #16843 – Remove unused deny selector logic in Rego policies
  • This PR removes unused deny selector logic from Rego policies that is no longer part of the active evaluation flow. The goal is to clean up dead code and improve maintainability. I’d like feedback on whether this removal is safe with respect to any existing or planned policy use cases.