GnuCash provides the following binary releases. When feasible and after testing, they can be updated to provide the new version. While the canonical repositories are on code, those are accessible only to the core team so the links are to the Github mirrors.
Keep in mind that these binary distributions are for ordinary users. As a general rule only stable release dependencies should be used for these packages. Exceptions may be made when an unstable release fixes a serious bug, but that should be discussed at length by the core team.
For developers with push privileges, unless you're able to
- test the new dependency version yourself,
- the upgrade is stable, and
- you're certain that there won't be a negative impact on users
create a pull request on Github so that others in the core team can test the change.
URLs and SHAs are stored in gnucash-on-flatpak/templates/org.gnucash.GnuCash.json.tpl.
- Repos, filenames and versions are stored in gnucash-on-windows/blob/master/gnucash.modules,
- on changes of major versions, adjust the include dirs in bundle-mingw64.ps1.
Nightlies are currently built for Flatpak and Windows. Ideally you would update the changes for both.
- Update workflow
- Download the .tar.gz file because Flatpak uses sha256, but aqbanking.de currently only displays MD5 checksums,
- Copy the URL into your Flatpak PR (in Redmine each file version has a unique file number directory),
- Copy the relevant parts into branch.module and version of your Windows PR
md5sum *.tar.gzwith the website,
- Copy the output from
sha256sum *.tar.gzinto Flatpak's sha,
- Create PRs on gnucash-on-flatpack and gnucash-on-windows.
- Bundling unstable dependencies
- Enable debug symbols (-g) also on this modules. More detailed stack traces will help their developers to fix critical bugs faster.