-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Release Che 7.23.1 #18577
Comments
@nickboldt please, make sure that #18631 is merged before releasing che-server |
FYI #18631 is merged, so the release can be started |
GH action for che-release isn't working (missing keys/token/perms for the gh checkouts) so running 7.23.1 the old way with https://ci.centos.org/job/devtools-che-release-che-release/254/console |
died building che server.
https://ci.centos.org/job/devtools-che-release-che-release/255/console kicked to rebuild che and images and operator... |
Hosted Che has been updated to the latest |
Community PRs not all merged. operator-framework/community-operators#2906 |
last PR merged. |
List of pending issues / PRs
[Hosted Che] Failed to rollout 7.23.0-SNAPSHOT - Jwks endpoint url not found in keycloak [Hosted Che] Failed to rollout 7.23.0-SNAPSHOT - Jwks endpoint url not found in keycloak #18553 / Fix che-server when used external oidc provider. #18563 slipped to Che 7.23.1, so need to verify it's backported correctly - Fix failing Che when used external OIDC provider. Port to 7.23.x #18631
description #xxx https://github.com/eclipse/che/issues/xxx
Release status
In series, the following will be released via che-release:
Then, these steps will be done, which still require some manual intervention (PR verification is not yet automated):
If this is a .0 release:
eclipse/che-theia
eclipse/che-machine-exec
eclipse/che-plugin-registry
eclipse/che-devfile-registry
che-dashboard
che-workspace-loader
eclipse/che-server
,eclipse/che-endpoint-watcher
,eclipse/che-keycloak
,eclipse/che-postgres
,eclipse/che-server
,eclipse/che-e2e
eclipse/che-operator
The text was updated successfully, but these errors were encountered: