Skip to content
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.

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

[Feature]: Versioned renovate presets #1829

Open
mrednic-1A opened this issue May 28, 2024 · 0 comments · May be fixed by #2877
Open

[Feature]: Versioned renovate presets #1829

mrednic-1A opened this issue May 28, 2024 · 0 comments · May be fixed by #2877
Labels
enhancement New feature or request priority:low

Comments

@mrednic-1A
Copy link
Contributor

mrednic-1A commented May 28, 2024

Context

Today we have renovate presets for o3r projects, for sdks which can be targeted via an url by other projects.
The problem is that we target always a preset from main branch.
For instance if a new postupgrade script is introduced in main branch for sdks, the older versions will not have it and in the sdk repo which targets the preset, the new postupgrade script might not exist.

Proposal

The idea will be to give the possibility to target presets from release versions (tags ?).
We need to investigate that it works properly (supported but not used a lot)
We need a renovate rule to update the renovate config (if we specify a version)

@mrednic-1A mrednic-1A added the enhancement New feature or request label May 28, 2024
@kpanot kpanot linked a pull request Feb 20, 2025 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority:low
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants