We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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-devfile-registry
eclipse/che-plugin-registry
che-dashboard
che-workspace-loader
eclipse/che-server
eclipse/che-endpoint-watcher
eclipse/che-keycloak
eclipse/che-postgres
eclipse/che-e2e
eclipse/che-operator
The text was updated successfully, but these errors were encountered:
@mkuznyetsov @nickboldt please, let us know once the artifacts are available on the central - we are planning to promote 7.26.0 to staging today - redhat-developer/rh-che#2043
7.26.0
Sorry, something went wrong.
@ibuziuk che-server images have been built about hour ago, and artifacts were released on nexus, though I don't see them available on Central yet
release is complete, community operator PRs are merged
che-docs PR was stuck, but it's been approved and merged now.
eclipse-che/che-docs#1848
mkuznyetsov
No branches or pull requests
List of pending issues / PRs
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-devfile-registry
eclipse/che-plugin-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: