[BUG] - qhub-dask hasn't been updated from 0.3.13 and is inconsistent with docs

OS system and architecture in which you are running QHub

all

Expected behavior

dask-qhub pins seem to be inconsistent across the repo.

In dask-worker yaml we have:

name: base
channels:
  - conda-forge
dependencies:
 # dask
 - qhub-dask==0.3.13

But in docs we say to use:

      - qhub-dask==||QHUB_VERSION||

This should mean use dask-qhub 0.4.1 but only 0.4.0 exists on conda-forge. Even just specifying qhub-dask without a pin should bring in 0.4.0

Actual behavior

This could potentially cause problems if we are using different versions of distributed and dask-gateway in end user environments from what is present in the dask-worker.

How to Reproduce the problem?

N/A

Command output

No response

Versions and dependencies used.

No response

Compute environment

No response

Integrations

Dask

Anything else?

1. We should add to the release checklist some steps to keep the versions of dask/distributed/dask-gateway + qhub-dask updated properly in the codebase and on condaforge
2. I think we need to explore whether we need to pin all three dask/distributed and dask-gateway or whether we can get away with just pinning gateway and maybe distributed. There are lots on few features being added to Dask very rapidly nowadays and being able to use the latest Dask is a high priority. This might need to break out into a new issue.

[dharhas]

I think so.

[viniciusdc]

I will be closing this issue as completed, due to its requirements already being completed:

We should add to the release checklist some steps to keep the versions of dask/distributed/dask-gateway + qhub-dask updated properly in the codebase and on condaforge I think we need to explore whether we need to pin all three dask/distributed and dask-gateway or whether we can get away with just pinning gateway and maybe distributed. There are lots on few features being added to Dask very rapidly nowadays and being able to use the latest Dask is a high priority. This might need to break out into a new issue.

I will open a separate issue to address how we should move forward updating qhub-dask