-
Notifications
You must be signed in to change notification settings - Fork 3
Description
With the restriction for diconium externals, the management of the version is sometimes challenging.
For example we have a team, which can only work on QA environment and does not has access to the dashboard, therefore we set the version to "latest" for those components.
That prevents us from developing component further on dev with newer version, since stage would be updated too.
To mitigate this issue, we could enhance the "latest" options.
For example with latest < 1.2.0.
Which means, give me the latest version smaller then 1.2.0.
That could result in the case, that on QA
the team can still publish version < 1.2.0 and the would receive updates in QA without having access (for example 1.1.9, 1.1.10 ... etc.), while
on dev environment we use the latest option and another team is already > 1.2.x
What do you think about it?
Might be useful for other parallel development cases too.
Any improvements to suggest?
Best Torsten