brasero changes the typelib version for BraseroBurn and BraseroMedia with each new upstream release, as it encodes the package version.
This looked wrong to me, so I asked around on #gnome-hackers:

<mbiebl> is there some documentation available how typelib versioning should be handled?
<mbiebl> I see that brasero encodes the upstream version number, e.g. BraseroMedia-3.4.1.typelib, which seems wrong
<ebassi> mbiebl: you want the version of the API
<ebassi> mbiebl: so if brasero changes version between 3.4.1 and 3.4.2, you really want that number
<mbiebl> ebassi: so, basically the SOVERSION of the library it references?
<mbiebl> or put differently, if the SOVERSION is bumped, the typelib version should be as well
<ebassi> mbiebl: it depends on policy of the library; e.g. gtk+'s typelib is Gtk-3.0, because the API is changed only with major version bumps
<ebassi> mbiebl: but yes: if you change the API, you bump the soname and you also bump the typelib/gir
<ebassi> given that the typelib reflects the ABI
<mbiebl> ebassi:  brasero uses /usr/lib/libbrasero-media3.so.1.2.0, so I guess 3.1 for the typelib version would look reasonable?
<mbiebl> ebassi: does that sound about right?
<ebassi> mbiebl: yeah
<mbiebl> ok, thanks


Attached is a patch, which uses  brasero-major-version.SOVERSION, i.e. 3.1 atm.