Skip to content

fix(deps): update canvas for GCC 15 source builds - #1

Merged
juan-fernandez merged 1 commit into
juan-fernandez:developfrom
anmarchenko:bug/2545_update-canvas-gcc15
Nov 9, 2026
Merged

juan-fernandez merged 1 commit into
juan-fernandez:developfrom
anmarchenko:bug/2545_update-canvas-gcc15

Conversation

@anmarchenko

Copy link
Copy Markdown

📑 Summary

Shepherd's scheduled Mermaid setup intermittently fails on Ubuntu 26.04 when canvas cannot download a prebuilt binary and falls back to compiling with GCC 15. canvas@3.2.0 omits <cstdint> in CharData.h, so compilation fails before any Test Optimization workload runs.

Raise Mermaid's canvas development dependency from ^3.2.0 to ^3.2.3 and regenerate the pnpm lockfile. This consumes the existing upstream fix in Automattic/node-canvas#2546 rather than maintaining another native-source patch.

Failing scheduled runs:

📏 Design Decisions

Only the canvas requirement and generated lockfile change. The lockfile also normalizes existing debug optional-peer snapshots; unrelated package versions remain unchanged. The playground's test workloads and Shepherd assertions stay intact.

Validation:

  • Clean Ubuntu 26.04 arm64 container, Node 22.14.0, GCC 15.2: forced canvas 3.2.0 source build reproduces the exact missing <cstdint> error; forced canvas 3.2.3 source build passes. Pixel rendering, font measurement, and PNG output pass.
  • Prescribed pnpm 10.30.3 frozen install and build pass. Completed pending native builds with pnpm rebuild --pending before runtime validation.
  • Full ESLint, Jison lint, and Prettier checks pass through pnpm test.
  • Unit run: 4,009 passed, 12 skipped, two todo. One documentation suite cannot load because it reads ../mermaid/package.json; the identical failure reproduces at unchanged base a2b9e5a71 in a separate worktree. No failing runtime tests remain.
  • pnpm test:check:tsc, lockfile contribution checks, and git diff --check pass.
  • Hosted check results are pending; the evidence above is from local validation.

📋 Tasks

  • Read contribution guidelines.
  • Reproduce the failed native build and verify the fixed release.
  • Run existing runtime, formatting, and TypeScript checks; document the unchanged documentation-suite failure.
  • No release changeset or product documentation needed for a playground development-dependency update.

@juan-fernandez
juan-fernandez merged commit a428ea3 into juan-fernandez:develop Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants