This update accommodates the additional macro restrictions introduced by Blizzard in patch 11.0.0. Those restrictions, not documented in the patch notes, amount to the following: commands in macros may not trigger the execution of any additional macros. This imposes some limitations on macro length, and on interactions between action bars, macros, and addons. For example, macros that /click action bar buttons containing a macro will not cause that macro to execute.
If you were using M6 macros via M6-configured key bindings, things should work mostly as before. Length restrictions may apply; macros may behave differently than prior to patch 11.0.0. If you experience problems, report an issue including your macro text.
If you were dragging M6 macros onto your action bars and using action bar-managed key bindings, M6 macros dragged onto action bars will continue to provide action feedback as before, but you will need to set up (conditional) bindings via M6 to allow macro execution.
Alt+Left clicking on the binding button in the M6 macro editor allows you to specify a conditional binding for the macro, using the secure command options syntax. For example, if your macro is on an always-visible action bar slot bound to Shift+X, you might enter [novehicleui] SHIFT-X as the conditional binding for the macro; if it was on the second page of your main action bar and bound to the = key, you might enter [novehicleui,bar:2] = as the conditional binding. Attempting to execute the M6 macro from the action bar will display an error message in chat, including a guess at the appropriate condition(s) to use for the binding.
If you were dragging M6 macros onto your action bars and clicking them directly, fun has been detected and summarily eliminated — there is no way to preserve pre-11.0 behavior without support from the action bar side. An alternative might be to use M6 macros via OPie instead.
Fixed an issue preventing [spec] conditions from being satisfied in M6 macros in Classic Era/Season of Discovery.