bbhtt

See https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#rstclass Hides duplicated headers for docs imported from Flatpak Closes https://github.com/flatpak/flatpak-docs/issues/436

Dependabot updater fails on PyGobject

2

### Is there an existing issue for this? - [X] I have searched the existing issues ### Package ecosystem pip ### Package manager version _No response_ ### Language version Python...

Add docs on using flatpak as a developer platform

1

Fixes https://github.com/flatpak/flatpak-docs/issues/4 Fixes https://github.com/flatpak/flatpak-docs/issues/13

Generates wrong links with Docusaurus 3.4.0

3

It is generating wrong links for example searching for "linter errors" and clicking the first result should go to https://docs.flathub.org/docs/for-app-authors/linter#linter-errors but the generated link goes to https://docs.flathub.org/docs/for-app-authors/linter/docs/for-app-authors/linter#linter-errors

Dark theme lost in preview window in 1.15.8

3

1.15.7:  1.15.8:  I'm guessing it's from https://github.com/lwindolf/liferea/commit/eb0ce6356df5874726563da347b1d828bc258e08

Hi, it'd be nice if this allowed setting a custom driverdir like intel-vaapi-driver and _then_ fallback to libva pkgconfig dir. See https://github.com/intel/intel-vaapi-driver/blob/06c9a893581c975c365c2281a1e597197b558085/meson.build#L41-L52

Add that `/var/run` or subpaths cannot be exposed when symlinked on host

1

Flatpak internally sets up a /var/run to /run symlink https://github.com/flatpak/flatpak/blob/fd1b7e444016d1b44bdab7cb5642b0ac83bd4b9e/common/flatpak-run.c#L2281. If it is symlinked on host too, when using `--filesystem=var/run/subpath` bwrap gets called twice to create the same symlink and...

test run https://github.com/bbhtt/flat-manager/actions/runs/13182106283

flatpak-builder sometimes creates duplicate groups in metadata

2

### Checklist - [X] I agree to follow the [Code of Conduct](https://github.com/flatpak/flatpak/blob/master/CODE_OF_CONDUCT.md) that this project adheres to. - [X] I have searched the [issue tracker](https://www.github.com/flatpak/flatpak-builder/issues) for a bug that matches...

Upstream go changes frequently break the external vendoring process, and we can't invoke the "official" vendoring process (`go mod vendor`) as the entire build process runs offline. It'd be nice...