Example
vs
sing-box-1.12.17 for OpenWrt 25, sing-box_1.12.22 for OpenWrt 24. wtf?
Is there a responsible person who monitors updates? How often should the repository pull new packages? Now this looks illogical and irresponsible, considering that in fact the actual version should be 1.13.2
https://github.com/openwrt/packages/commits/openwrt-25.12/net/sing-box - contact the guy making changes directly if you're looking for technical reply.
Lower your expectations and your life will become easier. You're not going to get the latest kernel, libc, packages even in rolling release style of distributions 
Oh, thank you, now I understand where this is coming from
I'm not justifying decision (or lack thereof) I'm just telling how community projects work. Addressing package maintainer is the right thing to do.
Also, back in the days nobody thought of OpenWrt as an end-user product. It was a platform for network operators and developers.
So if a package is too old or not maintained setup your own feed and or compile your own packages or firmware…
Best case of an outcome is to handing in patches so that the community benefits from it.
Community effort ... that "responsible person" could be you.
There is no staff paid to take care of things. Just volunteers, like you and me.
When somebody interested in the package backports, compiles and tests the new version for the specific release beach. Could be the "maintainer", could be you.
Backporting may be just a simple cherry-pick (Very possible in this case), but if there are deviating changes in the core OpenWrt or dependency packages, it could be more complicated.
History: https://github.com/openwrt/packages/pulls?q=is%3Apr+sing-box+is%3Aclosed
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.