> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: stefankangas@gmail.com, luangruo@yahoo.com, raman@google.com,
>  joaotavora@gmail.com, emacs-devel@gnu.org
> Date: Sun, 24 Dec 2023 16:59:11 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > But such breakage happens at times anyway, when some macros change in
> > incompatible ways and files that have the old versions of those macros
> > compiled into them are not recompiled.  It isn't anything new for
> > people who regularly update from Git and rebuild Emacs.
>
> The main problem is that with org-assert-version, "from time to time"
> becomes more frequent as the breakage is guaranteed every time a new
> version of Org is installed into Emacs tree.

If org-assert-version is the source of breakage, then that's not the
breakage I was talking about.  I was talking about breakage due to
changes in macros that were the motivation for you to introduce
org-assert-version in the first place.

IOW, instead of _inducing_ a breakage via org-assert-version, you
should let stuff break by itself, when an incompatible change is made
in one of the macros which org-assert-version protects.