Skip to content

[CI] Update app helpers/resources for debian/13.0.5 #2773

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
yunohost-bot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[CI] Update app helpers/resources for debian/13.0.5 #2773

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 1 addition & 8 deletions docs/dev/50.packaging/15.resources.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ toc_max_heading_level: 2
# custom_edit_link: 'https://github.com/YunoHost/yunohost/blob/dev/src/utils/resources.py'
---

Doc auto-generated by [this script](https://github.com/YunoHost/doc/blob/8e6fc8404d42466b00ced76811e3ac61607097e4/scripts/resources_doc_generate.py) on 20/05/2026 (YunoHost version 12.1.40.1)
Doc auto-generated by [this script](https://github.com/YunoHost/doc/blob/a83b35a36f26d6f6c0b6dc626571b1022a6f55eb/scripts/resources_doc_generate.py) on 23/06/2026 (YunoHost version 13.0.5)

## Apt

Expand Down Expand Up @@ -431,7 +431,6 @@ The infos are used by [this script](https://github.com/YunoHost/apps_tools/blob/

The script will rely on the code repo specified in `code` in the upstream section of the manifest.

##### Strategy
The `autoupdate.strategy` is expected to be constructed like this: `latest_<gitforge>_<strategy>`

You need to replace the `<gitforge>` in the strategy name by either `github`, `gitlab`, `gitea` or `forgejo`, as the autoupdater supports:
Expand All @@ -448,13 +447,8 @@ And choose one strategy in the following ones:
- `latest_<gitforge>_tag` : look for the latest tag (by sorting tags and finding the "largest" version). Then using the corresponding tar.gz url. Tags containing `rc`, `beta`, `alpha`, `start` are ignored, and actually any tag which doesn't look like `x.y.z` or `vx.y.z`
- `latest_<gitforge>_commit` : will use the latest commit on GitHub, and the corresponding tarball. If this is used for the 'main' source, it will also assume that the version is YYYY.MM.DD corresponding to the date of the commit.

##### Specific branch
You might want the autoupdater to check a specific branch of the upstream repository. In this case, make use of the optional `branch` property, e.g. `autoupdate.branch = "other_branch_than_default"`.

##### Upstream repository
It is also possible to define `autoupdate.upstream` to use a different Git repository instead of the code repository from the upstream section of the manifest. This can be useful when, for example, the app uses other assets such as plugin from a different repository.

##### Regex to match upstream versioning
If the upstream project provides non-standard tag or release names, you can fix this, with a regex with a matching group.

For example, if tags look like `release-v4.1`, put:
Expand All @@ -465,7 +459,6 @@ autoupdate.version_regex = "^release-v(.*)$"

And the autoupdater will use the matched group (here: `4.1`) as the version.

##### Testing the autoupdate configuration locally
You can make sure that your autoupdate strategy is working well immediately (without waiting for the next check on the infra) by doing the following:

1. Clone the apps_tools repository: `https://github.com/YunoHost/apps_tools`
Expand Down
Loading