[06:47:07]
<Yunohost Git/Infra notifications> [searxng_ynh] ewilly merged [pull request #551](https://github.com/YunoHost-Apps/searxng_ynh/pull/551) : Upgrade to v2026.11.01
[06:47:12]
<Yunohost Git/Infra notifications> [searxng_ynh] ewilly deleted branch ci-auto-update-2026.11.01
[06:47:18]
<Yunohost Git/Infra notifications> [searxng_ynh] github-actions[bot] opened [pull request #552](https://github.com/YunoHost-Apps/searxng_ynh/pull/552) : Upgrade master from testing
[06:48:25]
<Yunohost Git/Infra notifications> [searxng_ynh] ewilly merged [pull request #552](https://github.com/YunoHost-Apps/searxng_ynh/pull/552) : Upgrade master from testing
[06:48:34]
<Yunohost Git/Infra notifications> [searxng_ynh] ewilly deleted branch master-promotion
[06:49:21]
<Yunohost Git/Infra notifications> [package_linter] Thovi98 [commented](https://github.com/YunoHost/package_linter/pull/196#issuecomment-6570976314) on [issue #196](https://github.com/YunoHost/package_linter/pull/196) Deprecated version resources warning and update php warnings: Thank you If someone could take these linter issues over Id be glad, as they dont seem to be related with my changes ...
[08:00:48]
<Yunohost Git/Infra notifications> [piped_ynh] orhtej2 merged [pull request #325](https://github.com/YunoHost-Apps/piped_ynh/pull/325) : Upgrade sources
[08:00:49]
<Yunohost Git/Infra notifications> [piped_ynh] orhtej2 deleted branch ci-auto-update-sources-7edd5bbf
[08:08:37]
<Yunohost Git/Infra notifications> [vaultwarden_ynh] ericgaspar pushed to testing: Update manifest.toml ([d9c8019c](https://github.com/YunoHost-Apps/vaultwarden_ynh/commit/d9c8019cfc7f449e853548a11d0b06aa7b913835))
[08:09:12]
<Yunohost Git/Infra notifications> [vaultwarden_ynh] ericgaspar opened [pull request #334](https://github.com/YunoHost-Apps/vaultwarden_ynh/pull/334) : Testing
[08:35:52]
<Yunohost Git/Infra notifications> [vaultwarden_ynh] ericgaspar merged [pull request #334](https://github.com/YunoHost-Apps/vaultwarden_ynh/pull/334) : Testing
[09:38:59]
<Salamandar> yeah, creating a common github/forgejo action is a good idea. I'm thinking that other apps might leverage this.
[09:39:21]
<Salamandar> yeah, but then a github action called from 2 small workflows would be better
[09:39:25]
<Salamandar> anyways
[09:40:11]
<Salamandar> ```
$ path="/"
$ echo "_${path%/}_"
__
$ path="/a"
$ echo "_${path%/}_"
_/a_
$ path="/a/"
$ echo "_${path%/}_"
_/a_
```
i'm thinking of replacing the if/then/else with that bashism, what do you think ? @m606:matrix.org
[09:45:36]
<Salamandar> tbh 150 lines of the build script is just reimplementation of our autoupdate stuff
[10:03:49]
<Yunohost Git/Infra notifications> [apps] yunohost-bot opened [pull request #3693](https://github.com/YunoHost/apps/pull/3693) : Add Curio to wishlist
[11:20:50]
<Yunohost Git/Infra notifications> [forgejo_ynh] Josue-T merged [pull request #229](https://github.com/YunoHost-Apps/forgejo_ynh/pull/229) : Testing
[12:30:14]
<m606> Indeed there are common stuff for what relates to manifest parsing. And Aleks has been hoping this script to become Python rather than bash in the future, also because some of it could be integrated to the core (so it would make sense to reuse Python helpers from the autoupgrade script). Typically that would be meant to evolve with packaging v3, i.e. have the part in the build script under the "YOU SHOULD NOT NEED TO EDIT WHAT FOLLOWS" comment integrated to the core, and only the part above in a app dedicated script or in whatever will such things be declared in packaging v3.
In a shorter term maybe, I have for project to adapt this script so that it is run by the CI given that the latter already spends the ressources to build NodeJS apps (or Go, or other demanding stack), so we could just get the built assets and upload them to a repo - an improvement in terms of energy-saving and of independance from Github. More info about this there: https://github.com/YunoHost/issues/issues/2281#issuecomment-6026853366
[12:38:49]
<m606> not sure which if/then/else you target - creating a new one in GH workflow to call specific steps? or replace existing ones in build script?
For the first one, I wouldn't mind, for the second I find the if/then/else easier to read, but could be open to it if you think that it really improves things or makes the code significantly shorter
[13:22:19]
<Yunohost Git/Infra notifications> [ntfy_ynh] orhtej2 merged [pull request #121](https://github.com/YunoHost-Apps/ntfy_ynh/pull/121) : Upgrade to v2.36.0
[13:22:22]
<Yunohost Git/Infra notifications> [ntfy_ynh] orhtej2 deleted branch ci-auto-update-2.36.0
[13:22:35]
<Yunohost Git/Infra notifications> [ntfy_ynh] orhtej2 closed [pull request #120](https://github.com/YunoHost-Apps/ntfy_ynh/pull/120) : Upgrade to v2.35.0
[13:22:36]
<Yunohost Git/Infra notifications> [ntfy_ynh] orhtej2 deleted branch ci-auto-update-2.35.0
[13:22:55]
<Yunohost Git/Infra notifications> [ntfy_ynh] orhtej2 opened [pull request #122](https://github.com/YunoHost-Apps/ntfy_ynh/pull/122) : Testing
[13:23:05]
<Yunohost Git/Infra notifications> [ntfy_ynh] orhtej2 merged [pull request #122](https://github.com/YunoHost-Apps/ntfy_ynh/pull/122) : Testing
[13:39:35]
<Salamandar> I was talking about the ones in the install/change_url/upgrade scripts, sorry ^^
[13:40:35]
<Salamandar> Yeah, i'd be more okay to integrate this as a github action, that way we can refactorize stuff behind the scenes and package code wouldn't have to be commit-pushed on hundreds of repos
[13:50:08]
<Salamandar> i'll try and do a mock up
[14:09:49]
<m606> I guess you meant you'd prefer core THAN github actions, right? I agree with your point
[14:12:45]
<Salamandar> no, i meant as an action i would prefer over a huge workflow
[14:12:56]
<Salamandar> here, with an action, the 3 github workflows become only this:
[14:12:56]
<Salamandar> https://aria.im/_bifrost/v1/media/download/Ad9DnusobI5rSkmfj3MdXDgUK3YbnsCkJM9Dt3nlq7R7_1tNAKWNOuB2MKyKsTmN6f8omNUTRaMERmRGnlBzYNJCehocGEVQAG1hdHJpeC5vcmcvU2ZrYkhiUU9wQkZMTG1raGlieEJvYUxG
[14:14:33]
<Salamandar> (the first action checks the `on.*` and sets variables appropriately. The second action would be the current content of the workflows)
[14:16:56]
<m606> so it is more of combining the 3 workflows in 1?
[14:20:15]
<m606> https://aria.im/_bifrost/v1/media/download/AVOv9el-2dveMnLHKbS0DR_RqFQNX2vuF_2iG3jwWJ_OKYIAiHvMNmfrfY1wjNBKmaMf6wlBw795SLAs7loosjlCehocg13AAG1hdHJpeC5vcmcvalR6VEllSWdRU0xrRWNvVGR3QndEc3h0
[14:20:16]
<m606> can we still for disable the one to happen on push on testing in this case?
[14:20:54]
<Salamandar> Ah, no, we can't disable one trigger for a workflow
[14:21:03]
<m606> ok, worst case just remove this one
[14:21:05]
<Salamandar> So yeah, it would need to be a separate workflow
[14:21:23]
<Salamandar> that would mean 3 workflows, yeah, but at least the code duplication would be very very minimal :)
[14:22:42]
<Salamandar> each workflow would be as small as that:
[14:22:44]
<Salamandar> https://aria.im/_bifrost/v1/media/download/AcOM-fpd3e0ATa9gosXcZovSgoZjMEbuLmFy8zx0Zknnj-zcwrwiG-0MPEgKLEuDjxkS9KCNc2PTVM9UKb5sbqVCehocp7oAAG1hdHJpeC5vcmcvWnB6akxXWnhVbk1DeHpYZ3JGR2Vkd2VX
[14:24:14]
<Salamandar> And under the hood, in the action that would be in a common repository, we can work without having the fear to update every repository
[14:25:15]
<m606> .github/actions/ynh-build would be a shortcut to another central repo?
[14:25:56]
<Salamandar> yes. For now it's just a local path in the same repository as the code, but it would be `yunohost/apps_tools/.github/actions/ynh-build@latest` or something
[14:26:51]
<m606> yes perfect
[14:27:29]
<m606> actually i guess I should PR apps tools to merge prebuild-app into it https://github.com/oleole39/prebuild-app
[14:28:44]
<m606> though it's mainly the doc left
[14:29:08]
<m606> so it could maybe be yunohost/apps_tools/prebuild_app/.github/actions/ynh-build@latest
[15:03:21]
<Yunohost Git/Infra notifications> [ntfy_ynh] csolisr opened [issue #123](https://github.com/YunoHost-Apps/ntfy_ynh/issues/123) : Enable Web Push to activate UnifiedPush
[16:08:46]
<Yunohost Git/Infra notifications> [apps_tools] oleole39 opened [pull request #77](https://github.com/YunoHost/apps_tools/pull/77) : Add prebuild_app folder
[16:10:13]
<m606> https://github.com/YunoHost/apps_tools/pull/77
> so it could maybe be yunohost/apps_tools/prebuild_app/.github/actions/ynh-build@latest (edited)
[16:11:00]
<Salamandar> Alright, let's work together on this PR :)
[16:24:15]
<Yunohost Git/Infra notifications> [apps_tools] Salamandar [commented](https://github.com/YunoHost/apps_tools/pull/77#issuecomment-6582295437) on [issue #77](https://github.com/YunoHost/apps_tools/pull/77) Add prebuild_app folder: So, the architecture i would suggest around this would be: * A github action, here, that would set up the environment, ...
[16:48:11]
<Yunohost Git/Infra notifications> [apps_tools] oleole39 edited [pull request #77](https://github.com/YunoHost/apps_tools/pull/77) : Add prebuild_app folder
[17:09:20]
<Yunohost Git/Infra notifications> [apps_tools] oleole39 [commented](https://github.com/YunoHost/apps_tools/pull/77#issuecomment-6583322616) on [issue #77](https://github.com/YunoHost/apps_tools/pull/77) Add prebuild_app folder: > * A github action, custom to each package, that would **only** do the build Do you refer here to the whole build sc...
[17:11:07]
<Yunohost Git/Infra notifications> [apps_tools] oleole39 [commented](https://github.com/YunoHost/apps_tools/pull/77#issuecomment-6583322616) on [issue #77](https://github.com/YunoHost/apps_tools/pull/77) Add prebuild_app folder: > * A github action, custom to each package, that would **only** do the build Do you refer here to the whole build sc...
[21:30:04]
<Yunohost Git/Infra notifications> [nextcloud_ynh] pohutukawa [commented](https://github.com/YunoHost-Apps/nextcloud_ynh/issues/920#issuecomment-6588931877) on [issue #920](https://github.com/YunoHost-Apps/nextcloud_ynh/issues/920) Minor point upgrade 35.0.1~ynh1 to 35.0.2~ynh1 fails: @ericgaspar Are there any other potential work-arounds or fixes (possibly) in the pipeline?
Id hate to fall behind secu...
[23:33:29]
<Yunohost Git/Infra notifications> [ntfy_ynh] yunohost-bot opened [pull request #124](https://github.com/YunoHost-Apps/ntfy_ynh/pull/124) : Upgrade to v2.37.1
[23:50:20]
<Yunohost Git/Infra notifications> Autoupdater just ran, here are the results:
- 96 pending update PRs
- 27 new apps PRs: 2fauth, actual, bonfire, dagu, dokos, drupal_cms, element-call, esphome, filerise, invoiceninja5, jackett, limesurvey, meilisearch, miniflux, mstream, ntfy, peertube-search-index, pocket-id, seaweedfs, send, snweb, sparkyfitness, tunarr, wanderer, warpgate, wekan, wikijs
- 9 failed apps updates: automad, benevalibre, digiscreen, galette, gamja, loki, lxd, projectsend, snappymail
See the full log here: https://paste.yunohost.org/raw/upexokedex
Autoupdate dashboard: https://apps.yunohost.org/dash?filter=autoupdate