Nick Boldt

> prepare assets > publish assets to the github release > dowload assets This is going to have to change soon -- ideally before the end of the year. See...

> how was it tested? Other than the automated checks, it was not manually tested.

@ibuziuk so should we merge this or wait until 7.62 / 3.6 when we're removing theia entirely...?

@themr0c: > I don't know why @MichalMaler and @themr0c are marked as reviewers: you can safely remove us from the reviewer list. If you need docs team reviewers, it should...

Note that as we switch to using PNC for maven builds, we need to ensure upstream che-server === downstream che-server. Once this is merged, we can then also remove this:...

> how was it tested? Other than the automated checks, it was not manually tested.

> @SDawley Pls have a look at https://github.com/eclipse-che/che-operator/actions/runs/3653537634/jobs/6173111961 ``` Error: Unable to resolve action `docker/build-push-action@v6`, unable to find version `v6` ```

if we move from alpine to ubi8, we can use https://github.com/eclipse-che/che-release/actions/workflows/update-base-images.yml to keep the base image updated to the latest UBI 8.x with ALLLL the security fixes.

@l0rd see https://issues.redhat.com/browse/CRW-2459 for future work to make it easier to consume CRW dockerfiles outside of brew process. That will give you some insights into what differences there are between...

I think what Fred is suggesting is that you could build the bits with YOUR key, not ours. All you need from our end is to clone this repo and...