# Changelog apps in interface?

**URL:** https://forum.yunohost.org/t/changelog-apps-in-interface/35763
**Category:** Discuss
**Tags:** yunohost, english
**Created:** [March 4, 2025, 9:40am UTC](https://forum.yunohost.org/t/changelog-apps-in-interface/35763 "2025-03-04T09:40:12Z")
**Posts on this page:** 14
**Page:** 1

<div class="post-metadata">

### Author: ![dosch](https://forum.yunohost.org/user_avatar/forum.yunohost.org/dosch/32/368_2.png) [@dosch](https://forum.yunohost.org/u/dosch)
#### Post date: [March 4, 2025, 9:40am UTC](https://forum.yunohost.org/t/changelog-apps-in-interface/35763/1 "2025-03-04T09:40:12Z")

</div>

Sometimes an app gets a _yunohost only_ update. The name changes then from `appversion~ynh2` to `appversion~ynh3`.

But where can I easily find the change log for these updates? I could look at github repos and track changes of files, but that seems rather a lot of work.

Is it ever considered to display a change log in the ‘System Update’ interface?

---

<div class="post-metadata">

### Author: ![jarod5001](https://forum.yunohost.org/user_avatar/forum.yunohost.org/jarod5001/32/5323_2.png) [@jarod5001](https://forum.yunohost.org/u/jarod5001)
#### Post date: [March 4, 2025, 10:21am UTC](https://forum.yunohost.org/t/changelog-apps-in-interface/35763/2 "2025-03-04T10:21:05Z")

</div>

> [@dosch](#):
>
> look at github repos and track changes

That’s the right way.

> [@dosch](#):
>
> but that seems rather a lot of work

Adding a changelog is in fact a lot of work, so it will complicate the maintainer work.

I have added a simple changelog page in the wiki of the package of lychee [here](https://github.com/YunoHost-Apps/lychee_ynh/wiki/Changelog)  
I did it mainly for me to have a clear view what I’ve done so far.  
There is something that can be done but it should not make maintaining apps heavy.

---

<div class="post-metadata">

### Author: ![dosch](https://forum.yunohost.org/user_avatar/forum.yunohost.org/dosch/32/368_2.png) [@dosch](https://forum.yunohost.org/u/dosch)
#### Post date: [March 4, 2025, 10:48am UTC](https://forum.yunohost.org/t/changelog-apps-in-interface/35763/3 "2025-03-04T10:48:47Z")

</div>

true.

The things is; I now look at this possible update:

`Nextcloud from 30.0.6~ynh2 to 30.0.6~ynh3`

This is a _very important_ app on this server; many users depend on it and nextcloud has gigabytes of data in it and I don’t want to run the risk of needles downtime because something breaks during the upgrade.

So to make a good decision, it would be good to know if this update is _adding albanse translation to the readme_ or _fixing a critical security vulnerability_.

I wish there was an easy way to find that out

---

<div class="post-metadata">

### Author: ![ljf](https://forum.yunohost.org/user_avatar/forum.yunohost.org/ljf/32/58_2.png) [@ljf](https://forum.yunohost.org/u/ljf)
#### Post date: [March 4, 2025, 11:00am UTC](https://forum.yunohost.org/t/changelog-apps-in-interface/35763/4 "2025-03-04T11:00:55Z")

</div>

> [@dosch](#):
>
> fixing a critical security vulnerability

If it’s the case, there is an announcement in the security forum: [Security - YunoHost Forum](https://forum.yunohost.org/c/announcement/security/12)

But i agree with you, a changelog could be useful (the last nextcloud update enable searching of collectives from the unified Nextcloud search).

---

<div class="post-metadata">

### Author: ![oberger](https://forum.yunohost.org/user_avatar/forum.yunohost.org/oberger/32/6081_2.png) [@oberger](https://forum.yunohost.org/u/oberger)
#### Post date: [May 21, 2025, 6:24am UTC](https://forum.yunohost.org/t/changelog-apps-in-interface/35763/5 "2025-05-21T06:24:45Z")

</div>

I second the need for changelogs. And checking which PR have been merged in GitHub is a pain, for the regular user.

As maintainers have to update the manifest, I think the burden to update a changelog file isn’t much work. And helps a great deal the end users IMHO.

I’ve been doing that for Debian packaging and clearly that wasn’t so hard.

---

<div class="post-metadata">

### Author: ![jarod5001](https://forum.yunohost.org/user_avatar/forum.yunohost.org/jarod5001/32/5323_2.png) [@jarod5001](https://forum.yunohost.org/u/jarod5001)
#### Post date: [May 21, 2025, 6:39am UTC](https://forum.yunohost.org/t/changelog-apps-in-interface/35763/6 "2025-05-21T06:39:31Z")

</div>

> [@oberger](#):
>
> isn’t much work

In fact it is

---

<div class="post-metadata">

### Author: ![dosch](https://forum.yunohost.org/user_avatar/forum.yunohost.org/dosch/32/368_2.png) [@dosch](https://forum.yunohost.org/u/dosch)
#### Post date: [May 21, 2025, 9:28am UTC](https://forum.yunohost.org/t/changelog-apps-in-interface/35763/7 "2025-05-21T09:28:46Z")

</div>

> [@jarod5001](#):
>
> In fact it is

Don’t knock yourself out in pursuasive argumentation 😉

I have no idea how much work it is. But people make updates for apps for a reason. There is no new Nextcloud update for nothing. If the person updating the YNH package at least writes down why it was time for an update (new Nextcloud released, security fix, better integration with YNH etc. etc.) and this is displayed in the update interface… it would be a giant step forward.

To make that change to YNH is probably a lot of work, but writing why you as a packager made an update to an app… shouldn’t be that hard… right?

---

<div class="post-metadata">

### Author: ![oberger](https://forum.yunohost.org/user_avatar/forum.yunohost.org/oberger/32/6081_2.png) [@oberger](https://forum.yunohost.org/u/oberger)
#### Post date: [May 22, 2025, 8:35am UTC](https://forum.yunohost.org/t/changelog-apps-in-interface/35763/8 "2025-05-22T08:35:00Z")

</div>

And in terms of ratio of time spent, it is better if one person (the maintainer) does the work once, instead of each of the many “sysadmins” doing the work in turn, as many times as there are deployments over YNH instances…

This doesn’t have to be mandatory, but the possibility of moving to such a habit (again, already practiced by packagers in Linux distros) would be a great improvement IMHO.

---

<div class="post-metadata">

### Author: ![dosch](https://forum.yunohost.org/user_avatar/forum.yunohost.org/dosch/32/368_2.png) [@dosch](https://forum.yunohost.org/u/dosch)
#### Post date: [May 29, 2025, 8:09pm UTC](https://forum.yunohost.org/t/changelog-apps-in-interface/35763/9 "2025-05-29T20:09:16Z")

</div>

It’s here?

My Calibreweb just gave me a very nice changelog!  
Doesn’t seem that hard afterall?

 ![Screenshot 2025-05-29 at 22.08.03](https://forum.yunohost.org/uploads/default/original/2X/4/4037c236f08353984e917e7841420bbcd66cb59f.png)

---

<div class="post-metadata">

### Author: ![dosch](https://forum.yunohost.org/user_avatar/forum.yunohost.org/dosch/32/368_2.png) [@dosch](https://forum.yunohost.org/u/dosch)
#### Post date: [July 19, 2025, 7:07pm UTC](https://forum.yunohost.org/t/changelog-apps-in-interface/35763/10 "2025-07-19T19:07:31Z")

</div>

Sadly not for Nextcloud…

 ![Screenshot 2025-07-19 at 21.07.12](https://forum.yunohost.org/uploads/default/original/2X/f/f9057704793d02bbcb0c57d77562425dd92ae641.jpeg)

---

<div class="post-metadata">

### Author: ![tituspijean](https://forum.yunohost.org/user_avatar/forum.yunohost.org/tituspijean/32/3584_2.png) [@tituspijean](https://forum.yunohost.org/u/tituspijean)
#### Post date: [July 19, 2025, 8:40pm UTC](https://forum.yunohost.org/t/changelog-apps-in-interface/35763/11 "2025-07-19T20:40:25Z")

</div>

This is still voluntarily done by the packagers, cf. [Documentation | Yunohost](https://doc.yunohost.org/packaging/doc#display-notes-only-for-a-specific-version)

---

<div class="post-metadata">

### Author: ![dosch](https://forum.yunohost.org/user_avatar/forum.yunohost.org/dosch/32/368_2.png) [@dosch](https://forum.yunohost.org/u/dosch)
#### Post date: [July 20, 2025, 8:34am UTC](https://forum.yunohost.org/t/changelog-apps-in-interface/35763/12 "2025-07-20T08:34:35Z")

</div>

So the functionality is there! That is the main thing; now to find a nice flow for packagers to do this.

---

<div class="post-metadata">

### Author: ![Josue](https://forum.yunohost.org/user_avatar/forum.yunohost.org/josue/32/933_2.png) [@Josue](https://forum.yunohost.org/u/Josue)
#### Post date: [July 20, 2025, 12:54pm UTC](https://forum.yunohost.org/t/changelog-apps-in-interface/35763/13 "2025-07-20T12:54:03Z")

</div>

Hello,

As a maintainer of about ~10 apps I would say that ideally we need to have some automation aroud this to have this deployed in the whole apps. As same as for auto update, auto patch and the update of the readme, we should have something for changelog. It could be by example based on the PR which was merged since the last release or the commit. To me creating a changelog I agree is not a big job but there are a lot of release for some app and it could take at some point an amount of time that I can’t invest for this. Of course, we can’t automate everything, but having a script which create the base automatically and then the packagers can customize it if needed would be really usefull.

---

<div class="post-metadata">

### Author: ![tituspijean](https://forum.yunohost.org/user_avatar/forum.yunohost.org/tituspijean/32/3584_2.png) [@tituspijean](https://forum.yunohost.org/u/tituspijean)
#### Post date: [July 26, 2025, 10:15am UTC](https://forum.yunohost.org/t/changelog-apps-in-interface/35763/14 "2025-07-26T10:15:55Z")

</div>

> [@dosch](#):
>
> That is the main thing; now to find a nice flow for packagers to do this.

Packagers can now use the `!changelog` keyword to add a pre-upgrade message for the version currently in the manifest. All the text after the keyword will be used for the message.

The existing `!bump` command can be preemptively used to increase the package version.
