build(deps): bump @rive-app/canvas-single from 2.37.5 to 2.37.7#2708
build(deps): bump @rive-app/canvas-single from 2.37.5 to 2.37.7#2708dependabot[bot] wants to merge 3 commits into
Conversation
Bumps [@rive-app/canvas-single](https://github.com/rive-app/rive-wasm) from 2.37.5 to 2.37.7. - [Changelog](https://github.com/rive-app/rive-wasm/blob/master/CHANGELOG.md) - [Commits](rive-app/rive-wasm@2.37.5...2.37.7) --- updated-dependencies: - dependency-name: "@rive-app/canvas-single" dependency-version: 2.37.7 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Build Branch
Static preview entry points
QR codes (mobile preview)
Integration commandsnpm (Android / Extension): Swift Package Manager (Apple): .package(url: "https://github.com/duckduckgo/content-scope-scripts.git", branch: "pr-releases/dependabot/npm_and_yarn/main/rive-app/canvas-single-2.37.7")git submodule (Windows): git -C submodules/content-scope-scripts fetch origin pr-releases/dependabot/npm_and_yarn/main/rive-app/canvas-single-2.37.7
git -C submodules/content-scope-scripts checkout origin/pr-releases/dependabot/npm_and_yarn/main/rive-app/canvas-single-2.37.7Pin to exact commitnpm (Android / Extension): Swift Package Manager (Apple): .package(url: "https://github.com/duckduckgo/content-scope-scripts.git", revision: "47e9092293bb844aa8fd48996679746f188eae71")git submodule (Windows): git -C submodules/content-scope-scripts fetch origin pr-releases/dependabot/npm_and_yarn/main/rive-app/canvas-single-2.37.7
git -C submodules/content-scope-scripts checkout 47e9092293bb844aa8fd48996679746f188eae71 |
There was a problem hiding this comment.
Web Compatibility Assessment
No findings. The diff only updates @rive-app/canvas-single from 2.37.5 to 2.37.7 in special-pages/package.json and package-lock.json; it does not touch injected runtime code, API wrappers/shims, DOM mutation logic, feature config, or platform entry points.
Security Assessment
No findings. The package has no npm dependencies/peerDependencies, the lockfile is aligned with the declared version, and the changed files do not affect captured globals, messaging transports, message bridge validation, origin checks, or iframe handling.
Risk Level
Low Risk: dependency metadata-only update for a special-pages Rive canvas runtime, with no injected/src or security-sensitive code changes.
Recommendations
No blocking recommendations. I verified npm ci --ignore-scripts and npm run test-unit --workspace=special-pages locally; both completed successfully.
Sent by Cursor Automation: Web compat and sec
|
Suggested comment for Cursor review (copy and paste as a new comment): Note: GitHub Actions bot cannot trigger Cursor agent directly. Please copy the above comment to invoke the review. |
There was a problem hiding this comment.
Stale comment
Dependency review for
@rive-app/canvas-single2.37.5->2.37.7: no blocking concerns found.Confirmed evidence:
- The PR only updates
special-pages/package.jsonandpackage-lock.jsonfor this package.- npm metadata is stable across the bump: MIT license, 0 dependencies, 12 packaged files. The unpacked bundle grows from ~5.79 MB to ~5.90 MB, expected for the bundled JS/WASM runtime.
- Local usage is limited to
special-pages/pages/onboarding/app/shared/components/RiveAnimation.js, used by the v3 Duck Player onboarding flow. That code setsenableRiveAssetCDN: falseand loads a local.rivasset, so the Rive asset-CDN path remains disabled.- Upstream changelog entries for
2.37.6and2.37.7are mostly renderer/runtime changes: compressed texture/KTX2 support, canvas/GL rendering fixes, init/load-error handling, and runtime safety fixes such as overflow/list-size validation and memory pressure fixes.npm audit --workspace=special-pages --omit=devreported 0 production vulnerabilities.Residual validation risk:
- Existing automated coverage exercises the v3 Duck Player step and toggle telemetry, but the screenshot test masks the Rive
<canvas>, so it does not directly assert rendered pixels or state-machine visual output. I ran the targeted v3 Duck Player integration tests and they passed, but a visual check of the v3 Duck Player animation is the remaining confidence gap for this renderer bump.Still needed:
- The dependency is still needed while v3 onboarding remains supported/tested. Since v4 appears to use video/static assets instead, removing Rive can be revisited when v3 onboarding is retired.
Verification run:
npm cinpm run build --workspace=special-pagesnpm run test-int --workspace=special-pages -- pages/onboarding/integration-tests/onboarding.v3.spec.js --grep "duck player step" --reporter listnpm audit --workspace=special-pages --omit=devNo separate fix PR drafted because I did not find a required code change for this update.
Sent by Cursor Automation: Review dependabot
[Beta] Generated file diffTime updated: Fri, 22 May 2026 10:34:56 GMT AppleFile has changed IntegrationFile has changed WindowsFile has changed |
There was a problem hiding this comment.
Dependency review for @rive-app/canvas-single 2.37.5 -> 2.37.7: no blocking concerns found.
Confirmed evidence:
- The PR only changes
special-pages/package.jsonandpackage-lock.jsonfor this direct production dependency. - Local usage is limited to
special-pages/pages/onboarding/app/shared/components/RiveAnimation.js, reached by the v3 onboarding Duck Player step. The wrapper setsenableRiveAssetCDN: falseand loads the local bundled.rivasset, so this bump does not introduce a new runtime network fetch path. - Package metadata is stable across
2.37.5and2.37.7: MIT license, 0 npm dependencies, 12 published files, no bundled deps. The unpacked package grows from ~5.79 MB to ~5.90 MB, consistent with an inline JS/WASM runtime update. - Upstream changelog entries for
2.37.6/2.37.7are renderer/runtime oriented: compressed texture/KTX2 support, canvas/GL rendering fixes, JS load-error handling, runtime validation/safety fixes, and memory-pressure fixes. I did not see changelog evidence of a new browser permission, dependency, or CDN requirement relevant to this repo’s current usage. npm audit --workspace=special-pages --omit=devreported 0 production vulnerabilities.
Coverage and residual risk:
- Existing onboarding integration coverage exercises the v3 Duck Player step and toggle telemetry. I also ran targeted v3 Duck Player tests after the bump and they passed.
- Remaining validation gap is visual fidelity of the Rive-rendered
<canvas>itself: the automated tests assert page behavior around the step, not pixel-level state-machine output. A quick manual visual check of the v3 Duck Player animation would be the only extra confidence I’d ask for, not a blocker.
Dependency need:
- The dependency is still needed while v3 onboarding remains supported. Since v4 appears to avoid Rive for this flow, removing
@rive-app/canvas-singlecan be revisited when v3 onboarding is retired.
Verification run:
npm cinpm pack @rive-app/canvas-single@2.37.5 --json --dry-runnpm pack @rive-app/canvas-single@2.37.7 --json --dry-runnpm audit --workspace=special-pages --omit=devnpm run build --workspace=special-pagesnpm run test-int --workspace=special-pages -- pages/onboarding/integration-tests/onboarding.v3.spec.js --grep "duck player step" --reporter list
No separate fix PR drafted because I did not find a required code change.
Sent by Cursor Automation: Review dependabot
There was a problem hiding this comment.
Dependency update review for @rive-app/canvas-single 2.37.5 -> 2.37.7:
No confirmed blocking concerns found.
Confirmed evidence:
- Diff only updates
special-pages/package.jsonandpackage-lock.json; the package still has0npm dependencies and the lockfile integrity matches npm metadata for2.37.7. - Local usage is limited to
special-pages/pages/onboarding/app/shared/components/RiveAnimation.js, reached by onboarding v3’s Duck Player step. - Upstream changelog for
2.37.6/2.37.7includes renderer/runtime fixes, compressed texture/ktx2 support, and JS load-error handling changes. These could affect Rive canvas rendering/load behavior, but no repo API usage change was required. npm audit --omit=dev --workspace=special-pagesreports0production vulnerabilities.
Validation run:
npm cinpm run build --workspace=special-pagesnpm run test-int --workspace=special-pages -- pages/onboarding/integration-tests/onboarding.v3.spec.js --grep "shows v3 flow" --reporter list->12 passed
Residual risk / test coverage:
- Existing v3 flow tests exercise the Duck Player page path and toggles, but screenshots mask the Rive canvas to avoid animation flake, so they do not prove pixel-for-pixel rendering equivalence. Given this is a patch bump with no new transitive deps and runtime smoke coverage passed, I do not think this needs a blocking fix.
Dependency need / alternative:
- The dependency is still needed for onboarding v3. Onboarding v4 appears to use video for the Duck Player animation path, so a future cleanup could remove Rive only if/when v3 and
RiveAnimationare retired or ported.
I did not draft a separate fixes PR because I did not find a concrete issue requiring code changes.
Sent by Cursor Automation: Review dependabot


Bumps @rive-app/canvas-single from 2.37.5 to 2.37.7.
Changelog
Sourced from @rive-app/canvas-single's changelog.
... (truncated)
Commits
3984a8achore: tag 2.37.795048a9fix: Make ViewModelInstanceTrigger keyable for Stateful Components (#12556) c...3ad1efaSupport ktx2 (#12385) f454e3170eb313226fix(js): catch errors when creating the renderer and send to Rive LoadError e...575568eFix render_canvas_prepass_multi GL flip pivot (#12488) db997822be1603626chore(runtime): resolve build error after merge conflicts (#12545) 320eff3f97b3c62c7feat(scripting_workspace): HLSLStructLayout v2 with per-resource stageMask (#...8a3046cchore(rive_native): build microprofiler behind a flag (#12514) 44ba1a605ecce3914fix: memory pressure during dart allocations from luau trampoline cal… (#1254...6d75a6dfix(scripting_workspace): HLSL export cleanup (#12512) 60b685278cDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Note
Low Risk
Low risk dependency-only bump; main risk is potential rendering/runtime regressions in pages that use Rive due to updated WASM/canvas code.
Overview
Updates the
special-pagesdependency on@rive-app/canvas-singlefrom2.37.5to2.37.7, with correspondingpackage-lock.jsonresolution/integrity updates.Reviewed by Cursor Bugbot for commit e468ced. Bugbot is set up for automated code reviews on this repo. Configure here.