packageA depends on packageB (this is not modeled by Orlo), thus they are normally released together.
When such a release is in progress, and packageA is SUCCESSFUL and packageB is IN_PROGRESS, a query to /info/packages/versions will give the new version of package A and the old version of packageB. This is a problem for software which treats them as inseparable.
Options considered:
Include IN_PROGRESS packages in the version
- current version would go backwards if it failed
- Inspect the release to see if a package is part of a release in progress before considering it the current version
packageA depends on packageB (this is not modeled by Orlo), thus they are normally released together.
When such a release is in progress, and packageA is SUCCESSFUL and packageB is IN_PROGRESS, a query to /info/packages/versions will give the new version of package A and the old version of packageB. This is a problem for software which treats them as inseparable.
Options considered:
Include IN_PROGRESS packages in the version