2026-08-10  Kjell Ahlstedt  <kjellahlstedt@gmail.com>

  2.89.0

2026-07-06  Kjell Ahlstedt  <kjellahlstedt@gmail.com>

  Gio::DBus::ActionGroup: Improve the test whether GDBusActionGroup is final

2026-07-05  Kjell Ahlstedt  <kjellahlstedt@gmail.com>

  Gio: Emblem and DBus::ActionGroup: Don't derive gtkmm__Gxxx types

  GEmblem and GDBusActionGroup are declared G_DECLARE_FINAL_TYPE.
  Add _DO_NOT_DERIVE_GTYPE, _ABI_AS_WITH_DERIVED_GTYPE and _STRUCT_NOT_HIDDEN
  to the corresponding glibmm classes.

2026-06-29  Kjell Ahlstedt  <kjellahlstedt@gmail.com>

  Glib::Markup::ParseContext: Add get_attribute_position()

  * configure.ac:
  * meson.build: Require glib >= 2.89.0
  * glib/src/markup.[ccg|hg]: Add ParseContext::get_attribute_position().
  Remove duplicate of MarkupError documentation.
  * gio/src/application.hg:
  * gio/src/settingsschema.hg:
  * gio/src/settingsschemakey.hg:
  * glib/src/varianttype.hg: Remove some _IGNORE() commands.

2026-06-29  Kjell Ahlstedt  <kjellahlstedt@gmail.com>

  Regenerate docs.xml and .defs files, using files from glib 2.89.1

  and update gio_docs_override.xml and glib_docs_override.xml.
  
  The .defs files have been generated with glibmm/tools/mmgir.


2026-06-25  Sam James  <sam@gentoo.org>

  Drop G_GNUC_CONST as in glib

  This mirrors 016829559e75a1be24d637cad958a2cb00c6791d in glib, where
  the attributes were dropped because their use was invalid.
  
  This fixes glibmm being miscompiled by trunk GCC.
  
  Bug: https://gitlab.gnome.org/GNOME/glib/-/work_items/3984
  Signed-off-by: Sam James <sam@gentoo.org>

2026-06-25  Sam James  <sam@gentoo.org>

  tools: drop G_GNUC_CONST for get_type with pointer argument

  GCC's documentation for the `const` attribute [0] says:
  > Note that a function that has pointer arguments and examines the data pointed
  > to must not be declared const if the pointed-to data might change between
  > successive invocations of the function.
  
  Note that "might change" here is quite aggressive: it includes "if the
  pointer escapes at all", e.g. if it's some malloc'd memory that gets reused
  internally later too without something resetting its lifetime.
  
  The `pure` attribute would be appropriate here *if* there's no state
  changes even on the first run.
  
  [0] https://gcc.gnu.org/onlinedocs/gcc/Common-Attributes.html#index-const
  
  Bug: https://gitlab.gnome.org/GNOME/glib/-/work_items/3984
  Signed-off-by: Sam James <sam@gentoo.org>