Repository navigation
fix(renovate): remove invalid 'fix' from matchUpdateTypes - #875
Conversation
|
@onemec is attempting to deploy a commit to the therealng's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Correct patch update matching renovate.json |
The patch-specific rule no longer matches fix updates. It continues to match patch updates and keeps its existing commit-message settings and labels. |
Priority:
Estimated code review effort: 1 (Trivial) | ~3 minutes
Change: Bug fix · Severity of issue fixed: Medium
Possibly related PRs
- sleepypod/core#870: This PR updates patch versions of
nextandeslint-config-next, the update category targeted by the changed Renovate rule.
Suggested reviewers: ng
Merge Risk: 
25e98
-
The configuration change addresses the reported Renovate validation error; no merge-blocking concern was identified.
Pre-merge checks: 
-
Check name Status Explanation Description Check Check skipped - CodeRabbit’s high-level summary is enabled. Title check The title clearly and concisely describes the main change: removing the invalid "fix" update type from the Renovate configuration. Linked Issues check Issue #862requires removal of the invalid"fix"value fromrenovate.jsonatpackageRules[7].matchUpdateTypes. The pull request removes that value and retains"patch", which preserves the rule…Out of Scope Changes check The reviewed change is limited to the matchUpdateTypesvalue required by issue#862. The summary reports no other file or behavioral changes.Docstring Coverage No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… Full details: Linked Issues check
-
Explanation
Issue
#862requires removal of the invalid"fix"value fromrenovate.jsonatpackageRules[7].matchUpdateTypes. The pull request removes that value and retains"patch", which preserves the rule target and resolves the reported schema error. No additional coding requirements are stated.
Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files.
-
Finishing Touches: 💡 1
-
🛠️ Fix failing CI checks: 💡
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
Comment @coderabbitai help to get the list of available commands.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
…RV and breathing references, and schedule library (#878) Promotes `dev` to `main` with personal sleep-stage models, a heart-rate estimator that stops guessing on weak signal, beat-to-beat heartbeat detection, Watch HRV and breathing references, a schedule library, and the Next.js 16.4.3 security upgrade. ## Changes - Personal sleep-stage models: train off the pod from the phone's feature contracts, run them on the pod, keep several per side, upload a `candidate.json` from Settings, and stage a side's nights with its model when switched on. Includes MCP tools (#855, #857–#860, #864, #866). - Biometrics calibration on one page, with frozen dataset export and profile fitting on a laptop (#836, #837, #841). - Heart rate: windows scoring below `heart_rate.minimumPeakScore` (default 0.4) now report no heart rate instead of a guess. In local replay this cut Watch HR error from 5.2 to 1.75 bpm on tuning nights and from 4.3 to 3.1 bpm on held-back nights, at about 75% coverage (#840). - Beat-to-beat heartbeat detection in the piezo-processor, stored per minute in a new `heartbeats` table. Vitals are unchanged. Heartbeat retries now use bounded, ordered backoff (#848, #865). - Apple Watch references: import breathing rate and HRV (SDNN), add a pod-vs-Watch deviation report with night-by-night charts on the calibration page, render Watch-only nights, and archive pod biometrics off the pod for long-term comparison (#842, #844, #845, #847, #867). - Read-only analysis snapshot export (DB backup + RAW window) and MCP tool. Health export uploads are no longer truncated at 10 MB (#843, #839). - Schedule library with switchable curves, alarm snooze length with Snooze taper, and independent tap actions for normal and while-ringing (#835, #861, #849). - Storage: eMMC endurance card, RAM-only journal, and flash write insights with recording controls (#838, #854). - Surface the frzWater tank level and sensHealth cover disconnects, and register `sensHealth`, `frzWater` and `lps` as known record types (#872, #877). - Fix the internet access toggle after a reboot and the false "firewall rules missing" notice. Also fix false high TEC and slow fan warnings on an idle pod, and grant the service user journal read access (#856, #809, #801). - Security: upgrade Next.js to 16.4.3 for three advisories and require patched Node.js in development and pod installs (#870, #868). - Add the Europe/Bucharest timezone, update dependencies, fix the Renovate config, and kill surviving mutants (#874, #851, #853, #875, #852). ## Migrations - Configuration DB: schedule library, stale gesture alarm field cleanup, side stage models and the active model, and alarm snooze (0028–0034). - Biometrics DB: reference samples, heartbeats, and 0031 (0031–0033). ## Deploy note #840 bumps the biometrics manifest to 1.1.0. Profile revisions pinned to the old manifest will report `PROFILE_INCOMPATIBLE` and must be re-proposed against the new one. ## Test plan - [x] GitHub checks on the `dev` head (`1fbb953f`): CI, Build & Package, Dev Release, Publish OpenAPI Spec, Ref Collision Check. - [ ] After merge, wait for "Analyze & Release" on the `main` merge commit, then `sudo sp-update main` once on a pod and confirm the service starts and migrations apply. - [ ] Re-propose any active biometric profile against manifest 1.1.0 and confirm it applies. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Fixes #862
Description
Removes the invalid update type
"fix"frompackageRules[7].matchUpdateTypesinrenovate.json. In Renovate, allowed update types aremajor,minor,patch,pin,pinDigest,digest,lockFileMaintenance,rollback,bump, andreplacement. Patch was already present in the array, so removing"fix"fixes the schema validation error while preserving the intended rule targeting.Summary by CodeRabbit