Patch release 0.1.1 pining bokeh

[ncclementi]

It's not clear that we can do a release 0.2.0 bumping up all the packages see

• Release 0.2.0 #526

However, due to the unpin version of bokeh in distributed the current runtime breaks the dashboard see #520.

Action items.

• Reverting the packages version of the runtime to the versions in 0.1.0 and add bokeh=2.4.3
• Do a release

[dchudz]

+1

[dchudz]

Reverting the packages version of the runtime to the versions in 0.1.0 and add bokeh=2.4.3

Do you really have to revert?

I'd expect the easiest we to do this kind of patch release is:

1. branch off the 0.1.0 tag
2. update the bokeh pin and tag as 0.1.1
3. release that

[ncclementi]

@dchudz there is already a plan of action, we don't want to do a release without reverting the updates because there are some broken things on newer versions plus some regressions we don't yet understand. If you want to learn more about that, read #526 but more specifically #500.

The release was a bit delayed due to other issues but now we should be good to go. I'll have the release done in the next hour, have a few things to take care of first.

[jrbourbeau]

@dchudz was just proposing an implementation for the same thing that wouldn't have required changes to main. In retrospect, @dchudz's suggestion is probably more lightweight than what we're doing. That said, since we've already reverted packages in main, let's just keep with the current plan.

The release was a bit delayed due to other issues but now we should be good to go. I'll have the release done in the next hour, have a few things to take care of first.

Cool -- thanks for handing this @ncclementi

[ncclementi]

Closing as the release has been done in both pypi and conda-forge

[jrbourbeau]

Woo -- thanks @ncclementi!