OSD v4.1.0 handling (impacts to M4, serverless)

[mnyrop]

Hi all, starting a new ticket to wrap additional context around #3783 and create a spot to discuss.

Recap:

• OSD v4.1.0 breaks tiling for IIIF image API sources that don't specify hard-coded sizes (e.g., serverless-iiif, cc @mbklein @mathewjordan)
  • See: Demo with OSD v3.1 (works)
  • See: Demo with OSD v4.1 (funky)
• Mirador v4.x alpha versions use the buggy OSD.
  • See: Demo with 4.0.0-alpha.1 (funky)
  • (This version is deployed to the Mirador demo, so users are using it if not deploying it)
• Progress/conversation so far with OSD maintainer(s):
  • OSD main branch includes working fix (see: Demo from HEAD)
  • Maintainer(s) waiting for major release to include fix (See: Version 4.1.0 breaks IIIF TileSource somehow openseadragon/openseadragon#2452 (comment))
  • @mbklein started discussion to advocate for an OSD v4.1.1 patched release before major version (See: Any chance for a 4.1.1 release? openseadragon/openseadragon#2501)

Some questions/ideas:

• Can Mirador v4.x-alpha roll back to OSD v3.1.0 or v4.0.0?
• If not, can the prod Mirador 4-RC wait until a fixed OSD is available?
• Anyone from Mirador able to chime in over on the OSD discussion? Any chance for a 4.1.1 release? openseadragon/openseadragon#2501 to coordinate?

Thanks for your time! Hopefully this verbose ticket will help coordinate across OSD, Mirador, and Serverless-IIIF since the issue exists ambiguously between them.

[mbklein]

OpenSeadragon v4.1.1 has been released with a fix for this issue. It might be worth updating

"openseadragon": "^2.4.2 || ^3.0.0 || ^4.0.0",

to something like

"openseadragon": "^2.4.2 || ^3.0.0 || ^4.0.0 <4.1.0 || ^4.0.0 >=4.1.1",

to specifically exclude the buggy version.