stable/presentation-time/presentation-time.xml

@@ -198,7 +198,7 @@
       </entry>
     </enum>
 
-    <event name="presented">
+    <event name="presented" type="destructor">
       <description summary="the content update was displayed">
         The associated content update was displayed to the user at the
         indicated time (tv_sec_hi/lo, tv_nsec). For the interpretation of
@@ -256,7 +256,7 @@
       <arg name="flags" type="uint" enum="kind" summary="combination of 'kind' values"/>
     </event>
 
-    <event name="discarded">
+    <event name="discarded" type="destructor">
       <description summary="the content update was not displayed">
         The content update was never displayed to the user.
       </description>

staging/drm-lease/drm-lease-v1.xml

@@ -120,7 +120,7 @@
       </description>
     </event>
 
-    <event name="released">
+    <event name="released" type="destructor">
       <description summary="the compositor has finished using the device">
         This event is sent in response to the release request and indicates
         that the compositor is done sending connector events.

tests/meson.build

 prog_scan_sh = find_program('scan.sh')
-dep_scanner = dependency('wayland-scanner', native: true)
+dep_scanner = dependency('wayland-scanner', version: '>=1.20.0', native: true)
 prog_scanner = find_program(dep_scanner.get_pkgconfig_variable('wayland_scanner'))
 
 libwayland = [

unstable/fullscreen-shell/fullscreen-shell-unstable-v1.xml

@@ -217,7 +217,7 @@
   </interface>
 
   <interface name="zwp_fullscreen_shell_mode_feedback_v1" version="1">
-    <event name="mode_successful">
+    <event name="mode_successful" type="destructor">
       <description summary="mode switch succeeded">
 	This event indicates that the attempted mode switch operation was
 	successful.  A surface of the size requested in the mode switch
@@ -228,7 +228,7 @@
       </description>
     </event>
 
-    <event name="mode_failed">
+    <event name="mode_failed" type="destructor">
       <description summary="mode switch failed">
 	This event indicates that the attempted mode switch operation
 	failed.  This may be because the requested output mode is not
@@ -239,7 +239,7 @@
       </description>
     </event>
 
-    <event name="present_cancelled">
+    <event name="present_cancelled" type="destructor">
       <description summary="mode switch cancelled">
 	This event indicates that the attempted mode switch operation was
 	cancelled.  Most likely this is because the client requested a

unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml

@@ -219,7 +219,7 @@
       'immediate_release' event it is automatically destroyed.
     </description>
 
-    <event name="fenced_release">
+    <event name="fenced_release" type="destructor">
       <description summary="release buffer with fence">
         Sent when the compositor has finalised its usage of the associated
         buffer for the relevant commit, providing a dma_fence which will be
@@ -236,7 +236,7 @@
       <arg name="fence" type="fd" summary="fence for last operation on buffer"/>
     </event>
 
-    <event name="immediate_release">
+    <event name="immediate_release" type="destructor">
       <description summary="release buffer immediately">
         Sent when the compositor has finalised its usage of the associated
         buffer for the relevant commit, and either performed no operations