Hey! First off, thanks for adding Flatpak support in #19749 — the generated-sources.json file is super useful for downstream packaging.
The problem
Right now, flatpak/generated-sources.json only lives on master and isn't part of tagged releases. The flatpak/ directory isn't included in the release tags at all (checked v1.16.3 through v1.16.6).
On top of that, the file on master was generated back on Feb 17 and hasn't been updated since, so it no longer matches the dependencies in newer releases. For example, several git deps point to different commits (node-crash-dump, 7z-bin, modmeta-db, etc.) and some npm packages are missing entirely.
Why it matters
We're packaging Vortex for nixpkgs and this file would be perfect for our offline build setup — it gives us all the yarn dependency URLs with checksums in one place. Without it, we have to merge ~50 yarn.lock files from across the monorepo ourselves.
But the file only works if it matches the source version being built. When the commits don't line up, the offline build fails with missing dependencies.
Would it be possible to...
- Run
flatpak_sources.py as part of the release process so generated-sources.json stays in sync
- Include the
flatpak/ directory (or at least the generated source files) in tagged releases
This would make life much easier for distro packagers. Happy to help test if needed!
Hey! First off, thanks for adding Flatpak support in #19749 — the
generated-sources.jsonfile is super useful for downstream packaging.The problem
Right now,
flatpak/generated-sources.jsononly lives onmasterand isn't part of tagged releases. Theflatpak/directory isn't included in the release tags at all (checkedv1.16.3throughv1.16.6).On top of that, the file on
masterwas generated back on Feb 17 and hasn't been updated since, so it no longer matches the dependencies in newer releases. For example, several git deps point to different commits (node-crash-dump,7z-bin,modmeta-db, etc.) and some npm packages are missing entirely.Why it matters
We're packaging Vortex for nixpkgs and this file would be perfect for our offline build setup — it gives us all the yarn dependency URLs with checksums in one place. Without it, we have to merge ~50 yarn.lock files from across the monorepo ourselves.
But the file only works if it matches the source version being built. When the commits don't line up, the offline build fails with missing dependencies.
Would it be possible to...
flatpak_sources.pyas part of the release process sogenerated-sources.jsonstays in syncflatpak/directory (or at least the generated source files) in tagged releasesThis would make life much easier for distro packagers. Happy to help test if needed!