Latest release is breaking custom ContentManager

[fcollonval]

Description

#1363 changed the ContentManager API in a breaking manner; this can be seen in mwouts/jupytext#1165
But I hit it too on private code.

Reproduce

Install jupytext

Expected behavior

The content manager get should be called without md5 if it does not support it.

Context

• Jupyter Server version: 2.11.0

Command Line Output

 TypeError: build_jupytext_contents_manager_class..JupytextContentsManager.get() got an unexpected keyword argument 'md5'

[marr75]

This also impacts the ploomber project.

It's disappointing that a breaking change was introduced without a major version or that an interface change that was non-breaking was not devised.

[blink1073]

I yanked 2.11.0. Please let's keep the tone civil, we're all volunteers doing our best, the breaking API change was unintentional.

[Wh1isper]

Sorry for the breaking changes to the API. I have created #1367 to fix this.

[m-rossi]

I also created a PR to mark the conda-forge-package as broken: conda-forge/admin-requests#864