Multiple ietf-netconf-server revisions shipped in /usr/share/yang/modules/libnetconf2/ – recommended pinning?”

[jaraj369]

We see both ietf-netconf-server@2023-12-28.yang and ietf-netconf-server@2025-04-24.yang installed.

Is shipping multiple revisions expected? If yes, what compatibility goal does it serve?
When both revisions are present, how should applications ensure they load the intended revision?
Is there an official recommendation for setting module search paths (e.g., YANG_MODPATH) or otherwise pinning revisions in production?

Thanks.

[michalvasko]

Is shipping multiple revisions expected?

There are never multiple revisions of a module shipped. You still have the old YANG module from a previous installation.

EDIT: I see that there indeed are 2 revisions of the module in the master branch. That was a bug, fixed in devel already.