chore(deps): update dissmodel requirement from >=0.5.0 to >=0.6.3 in /services/jupyter

[dependabot]

Updates the requirements on dissmodel to permit the latest version.

Changelog

Sourced from dissmodel's changelog.

[0.6.3] — 2026-07-16

Fixed

• mypy config: bumped python_version to 3.12 so NumPy 2.x stubs parse correctly, and added the missing type annotations in RasterBackend and dissmodel.io.raster that the stricter parse surfaced.

Changed

• README badges: refreshed the coverage badge (55% → 79%, stale since 0.6.1) and renamed the LambdaGeo badge label to DisSModel.

Internal

• JOSS paper (paper.md / paper.bib) revised in response to reviewer openjournals/joss-reviews#10827 contribution statement for all five authors, expanded the Research Impact Statement and AI Usage Disclosure, corrected reproducibility pointers and several bibliography entries, and trimmed the body text to fit the JOSS 1,750-word limit.

---

[0.6.2] — 2026-06-15

Fixed

• SyncRasterModel.synchronize(): state variables loaded as temporal (time, y, x) arrays (e.g. when CubeClient.to_lucc_data() finds temporal catalog entries) now correctly use the first slice as the initial _past snapshot instead of copying the full 3D array, which caused shift2d to crash with ValueError: too many values to unpack.
• _write_geotiff: casting a float array containing NaN to an integer dtype (e.g. int16) now fills NaN/inf with the band's nodata value before the cast, eliminating a RuntimeWarning: invalid value encountered in cast.

---

[0.6.1] — 2026-06-12

Fixed

• GeoTIFF write with mixed-dtype band_spec (e.g. int32 categorical + float32 continuous) silently truncated float bands to the first band's dtype. Bands are now promoted to the common NumPy result type (np.result_type) before writing.

Added

• Test suites for dissmodel.io (utils, dispatch, storage, raster, vector, convert, xarray) and dissmodel.visualization (chart, map, env detection). Coverage: 55% → 79% (319 → 441 tests).

Notes

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)