My company has been using hosted medplum in production for about a month on the "Production" plan. we were impacted by one of the breaking changes included in the v4 release https://github.com/medplum/medplum/pull/5631/files that was released on friday. how do teams who use the cloud hosted medplum test their code against upcoming releases? is there a beta channel available for hosted customers to test their applications against the unstable build?

Hi @Elliot sorry for the inconvenience. We have considered this version "stable", and we apologize fo rthte regression

as far as i can tell the change was intended to be backwards incompatible (it was listed as such under "breaking changes" for the v4 release https://github.com/medplum/medplum/releases/tag/v4.0.0), so it's not clear to me that there's a bug that needs to be fixed. My question is more if there's a way that customers using the cloud-hosted medplum can either 1. validate their application code against the next version of medplum using the cloud-hosted platform or 2. decide what time they want to opt in to the next medplum version to provide for sufficient time to test. If the answer is we need to have a self-hosted deployment available just for testing against the next release that is fine, but i just want to verify there isn't another option available

@rahul1 any update here?

@shirlay_2 thanks for yoru patience. As @Elliot identified, the real answer here is using a self-hosted system if you want full control over your upgrade cycle