You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ?).
To be analyzed.
The text was updated successfully, but these errors were encountered:
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 ?).
To be analyzed.
The text was updated successfully, but these errors were encountered: