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
{{ message }}
This repository has been archived by the owner on Mar 17, 2021. It is now read-only.
During the process for updating the upstream Che dependency version, we're stuck in a state where the PR-check CI job for the "update to version x" PR continues to use the previous versions registries (since it reuses the staging registries). I don't know of any specific issues related to different versions of Che vs. the registries, but this could potentially cause issues in the future.
Instead, the PR-check job should also deploy the relevant plugin and devfile registries, to make the check more accurate.
Background
Previously, the prod-preview registry was updated continuously, so when we created the "update to version 7.x" PR, the PR-check would use the current registry. Now that registries are pinned to the release-preview branch, they are left behind.
Description:
During the process for updating the upstream Che dependency version, we're stuck in a state where the PR-check CI job for the "update to version x" PR continues to use the previous versions registries (since it reuses the staging registries). I don't know of any specific issues related to different versions of Che vs. the registries, but this could potentially cause issues in the future.
Instead, the PR-check job should also deploy the relevant plugin and devfile registries, to make the check more accurate.
Background
Previously, the prod-preview registry was updated continuously, so when we created the "update to version 7.x" PR, the PR-check would use the current registry. Now that registries are pinned to the
release-preview
branch, they are left behind.Related
#936
The text was updated successfully, but these errors were encountered: