chore: stop the weekly novnc bump and report coverage on a red build

[KrasimirKralev]

Two small maintenance fixes, both found while verifying that earlier work actually holds.

The novnc pin was being rewritten every week. The manifest pins @novnc/novnc exactly, because 1.7.0 removes the subpath imports this codebase relies on. But that release is a minor, and the bun group only ignores majors — so the weekly run kept rewriting the pin and opening a PR that could never pass. Now that one bump, for that one package, is ignored. The comment says when to remove the rule.

Coverage numbers never appeared on a failing build. pr-tests-coverage.yml runs its parse step if: always(), with a comment saying that is precisely so the PR comment can show numbers even on failure — but Vitest does not write the summary when a test fails, so the step always took the not-found path. reportOnFailure: true makes the workflow do what it already claimed to do. The gate is unchanged: a failing test still fails the job.

Summary by CodeRabbit

• Tests

  • Coverage reports are now generated even when test runs include failures.

• Chores

  • Preserved compatibility with the current noVNC version by preventing unsupported minor updates.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: fc38e1bb-8517-4bd4-a078-6bdc27079fbf

📥 Commits

Reviewing files that changed from the base of the PR and between accbc70 and bacdb06.

📒 Files selected for processing (2)

• .github/dependabot.yml
• vitest.config.ts

---

📝 Walkthrough

Walkthrough

The pull request pins @novnc/novnc minor updates at 1.6.0 and configures Vitest to report coverage after failed test runs.

Changes

Dependency policy

Layer / File(s)	Summary
Pin incompatible noVNC minor updates .github/dependabot.yml	Dependabot ignores semver-minor updates for @novnc/novnc and documents the incompatible 1.7.0 exports.

Coverage reporting

Layer / File(s)	Summary
Report coverage after failures vitest.config.ts	Vitest writes coverage reports when tests fail while preserving the test failure status.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• ID-Robots/clawbox#299: Both changes modify Dependabot update policies.
• ID-Robots/clawbox#369: Both changes pin @novnc/novnc at version 1.6.0.

Suggested reviewers: georgik77, yalexx

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description clearly explains both changes and their reasons, but it omits the template's type, testing, and checklist sections.	Add the change type, testing commands and results, checklist confirmations, and screenshots or logs if applicable.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes both maintenance changes: stopping the noVNC bump and reporting coverage on failed builds.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/dependabot-and-coverage-report

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🦀 ClawReview

Scuttled over to say hello and get you oriented 🦀

Two CI housekeeping fixes. The Dependabot config now ignores minor-version bumps for @novnc/novnc — 1.7.0 is a breaking change in minor clothing that drops the subpath imports the codebase relies on, and without this rule the weekly run kept reopening a PR that could never pass. The Vitest config adds reportOnFailure: true so the coverage summary is written even when tests fail, letting the PR comment workflow actually show numbers on a red build as it was already designed to do.

At a glance

• 🧹 Chore · touches GitHub Actions CI config (Dependabot + coverage workflow) and Vitest config
• Base branch: beta · +17 source / +0 tests across 2 files
• ✅ base beta matches the beta-first convention
• ✅ conventional PR title

Good to know

• ℹ️ No runtime or customer-facing code touched — pure CI and tooling config.
• ℹ️ The @novnc/novnc pin guard (src/tests/unit/novnc-pin.test.ts) and a TODO comment in dependabot.yml mark when to revisit the ignore rule.

_{— ClawReview 🦀, scuttling off. General info only — see CodeRabbit for the detailed review. Conventions: docs.}

[github-actions]

CI Summary

✅ Tests

• Result: passed
• View run
• Coverage: statements 65.17%, branches 54.15%, functions 63.12%, lines 67.25%

✅ E2E

• Result: passed
• View run

✅ E2E Install

• Result: success
• View run