Moved to GitLab: https://invent.kde.org/wrobelda/vcpkg/-/issues/4

@ostroffjh Agreed. The AppStream spec defines the following:

@atem it could be in both, an automatic job to push the appstream xml from kmymoney repo to kmymoney-org would be easy to add. Still, better to use a single source and kmymoney own repo is best suited for this.

@ognarb agreed, this is a better, universal solution

@cullmann I will do my best to try and test it with KMyMoney on macOS and maybe Windows this coming weekend. I'll keep you posted.

@atem You could use something like this:

Checked the 5.x branch code and can no longer find any usage of "${DATA_INSTALL_DIR}/appdata/"

@atem I don't see why this would be a problem at all for automation, we can maintain multiple stable release placeholders in _config.yml for both KMyMoney5 and KMyMoney4 stable branches and it is absolutely not a problem to make Gitlab Pipelines aware of that.

This is outdated by now.

All theming related issues were migrated to Invent: https://invent.kde.org/office/kmymoney/-/issues

Discussion moved to Invent: https://invent.kde.org/office/kmymoney/-/issues/16

The discussion has moved to GitLab: https://invent.kde.org/office/kmymoney/-/issues/2

Discussion moved to Invent: https://invent.kde.org/office/kmymoney/-/issues/14

The discussion has moved to GitLab: https://invent.kde.org/office/kmymoney/-/issues/2

The discussion has moved to GitLab: https://invent.kde.org/office/kmymoney/-/issues/4

When it comes to automation, it is a perfect job for GitLab pipelines which can handle additional steps post-release. What I suggest is that the pipeline auto-updates the version.yml file with most recent version, and the version.yml to be incorporated into the html.

@cullmann is this still planned to be released?