Yes. Our next release is planned for 4th of Aug, however, if we need to support an unsuspended provider like Beam, it might be more involved. I would say we will anyhow have to make an exception ad-hoc release whenever Beam is released - that seems quite a bit safer than mixing it with other provider releases.
We have to account for the four-day cooldown required for installing dependencies and rebasing and merging the "revert" PR and add >= 2.76.0 (there might be some surprises to fix - dependency resolution is too complex to make 100% predictions. This means that whenever Beam client 2.76.0 is released, we will either need to wait 4 days or add a temporary exception to the cooldown (and remove it after), and make sure that all our tests pass after we add >= 2.76.0 in our deps. So it's anyhow a more involved thing than a regular release. I would say releasing 2.76.Releasing 2.76.0 by the end of July could allow us to add it to the "regular" wave to give us time to do all that - so I'd say it's quite unlikely. J.
