Wieland Lindenthal aeb5e34ea1 chore: upgrade @blocknote/* to 0.51, op-blocknote-extensions to 0.1.0 (FEASIBILITY) ...

Feasibility-study draft showing the openproject-side consumer changes
that go with op-blocknote-extensions v0.1.0 (opf/op-blocknote-extensions
PRs #133 and #134, not yet merged):

frontend
- @blocknote/{core,mantine,react}: ^0.44.2 → ^0.51.0
- op-blocknote-extensions: v0.0.26 → v0.1.0 (URL not live yet)
- OpBlockNoteEditor.tsx: BlockNote 0.51 tightened CollaborationOptions —
  omit the whole `collaboration` block when no hocuspocusProvider is
  wired up; cast the provider at the boundary because Hocuspocus's
  `awareness: Awareness | null` doesn't match BlockNote's
  `Awareness | undefined`.

hocuspocus (extensions/op-blocknote-hocuspocus)
- @blocknote/server-util: ^0.44.2 → ^0.51.0
- @blocknote/core (dev): ^0.44.2 → ^0.51.0
- op-blocknote-extensions: v0.0.18 → v0.1.0
- openProjectApi.ts: import the static specs from the new
  `op-blocknote-extensions/server` subpath (keeps @blocknote/react out
  of Node); align schema key with the post-refactor block type
  ("openProjectWorkPackage" → "openProjectWorkPackageBlock"); register
  the inline static spec so inline work-package chips survive the
  markdown export.

Lockfiles intentionally not regenerated: the v0.1.0 GitHub URL doesn't
resolve yet. Reviewers should treat this PR as a feasibility study, not
a mergeable artefact.

Refs: https://community.openproject.org/wp/74654

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2026-06-02 17:02:40 +02:00

..

op-blocknote-hocuspocus

chore: upgrade @blocknote/* to 0.51, op-blocknote-extensions to 0.1.0 (FEASIBILITY)

2026-06-02 17:02:40 +02:00