chore(deps): bump toml from 0.8.2 to 0.8.23 in /src-tauri in the cargo-minor-patch group - #3
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps the cargo-minor-patch group in /src-tauri with 1 update: [toml](https://github.com/toml-rs/toml). Updates `toml` from 0.8.2 to 0.8.23 - [Commits](toml-rs/toml@toml-v0.8.2...toml-v0.8.23) --- updated-dependencies: - dependency-name: toml dependency-version: 0.8.23 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: cargo-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Contributor
Author
|
Dependabot can't parse your Cargo.toml. Because of this, Dependabot cannot update this pull request. |
Contributor
Author
|
Looks like toml is no longer updatable, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/cargo/src-tauri/cargo-minor-patch-2599ad99c4
branch
July 8, 2026 07:53
This was referenced Jul 12, 2026
github-actions Bot
pushed a commit
that referenced
this pull request
Jul 15, 2026
Seventh PR of the v0.4.0/v0.5.0 transition. Doc-only. Auto-merge eligible per CLAUDE.md rule 2. What this ships: - docs/v0.5.0_plan.md — the v0.5.0 cycle scope and PR sequence. The cycle is named "Ground Truth" because the work is about validating the abstractions we shipped in v0.3 / v0.4 against real hardware, and adding the narrow features that real-car owners actually need first. Cycle spine (3 PRs, in order): - PR #1 — Real-car u8_enum validation harness. Doc-only. Mirrors the v0.4.0_first_pr.md shape. Gives an F/G-series owner with an ENET adapter a small checklist to validate the example enum DIDs (gear / engine_state / knock_detect) marked [needs verification] in b58.toml / n55.toml since PR #60. - PR #2 — Real-car fuel-trim / adaptation readout. Adds the DIDs (typically 0x4116 / 0x4117 / 0x4118 on BMW DME) and marks them [needs verification]. Likely no new decoder needed (existing s16_div100 handles the typical scaling). Protected path (live.rs is adjacent to protocol/). - PR #3 — Real-car knock-detection visualisation polish. Pure JS; extends the Logging tab's per-channel display to flag severity-bearing enum values (Moderate / Severe) with a visual indicator. Uses LiveValue.text from PR #60. Out of v0.5.0 scope (deferred to v0.6+ or Backlog per ROADMAP.md): OBDLink MX+, ENET/DoIP auto-detection, trigger- based logging, log merge/comparison, custom math channels, cloud sync, Pi CAN bridge, plugin system, Bootmod3, multi- language UI, web-based shared-log viewer. Each of those has a specific blocker documented in ROADMAP.md. The plan also explicitly notes: - Sibling-agent race in this repo (CLAUDE.md + multi-writer skill): work in fresh sibling clones, branch off origin/main, push from the clone. - origin/main drift (local main was stale vs origin/main during the v0.4 cycle): always git fetch origin before basing a branch, diff against origin/main not main. - CLAUDE.md rule 2: only doc-only PRs auto-merge. PRs #2 and #3 must go through human review. Verification: - node --test src/js/histogram.test.js → 13/13 (run via direct invocation; origin/main's package.json has a missing comma that breaks 'npm run test:*' — NOT fixed here, per commit-discipline 'discovering a broken sibling commit is not license to fix it'. That breakage is inherited from PR #68 / #69 area; a separate doc-only PR can fix it.) This PR does not touch code, workflows, or protected paths. 195 insertions in one new file. Co-authored-by: ohgeeceee <ohgeeceee@users.noreply.github.com>
github-actions Bot
pushed a commit
that referenced
this pull request
Jul 15, 2026
First PR of the v0.5.0 "Ground Truth" cycle. Doc-only. Auto-merge eligible per CLAUDE.md rule 2. What this ships: - docs/validation/u8_enum-validation.md — the actual validation harness. Pre-flight checklist (cable, adapter, ignition, simulator NOT in use), per-DID test procedure for the three example enum DIDs shipped in v0.4.0 (gear / DA0A, engine_state / 4004, knock_detect / 401F), results-submission instructions (PR the [verified YYYY-MM-DD] labels back into b58.toml / n55.toml), and a 'what if a byte doesn't match' section for the most-likely failure mode. - docs/v0.5.0_first_pr.md — the cycle's written record of why this PR exists. Mirrors the v0.4.0_first_pr.md shape so future contributors can follow the same pattern. Why this is the first PR of v0.5.0: The v0.5.0 cycle plan (docs/v0.5.0_plan.md, PR #70) lists three PRs in order: 1. THIS PR — validation harness (doc-only, lands first because it unblocks the rest) 2. Real-car fuel-trim readout (PR #2) 3. Real-car knock visualisation polish (PR #3) Real-car evidence was the only 🟡 blocker for the v0.4.0 'Tuner Friendly' cycle to retire. The example enum DIDs shipped in PR #60 all carry [needs verification] markers because the byte-to-state mappings came from OBDb (CC-BY-SA 4.0) and have not been validated on real hardware. This harness is the smallest possible next step for an F/G-series owner with an ENET adapter to retire that blocker: a checklist they can fill in and PR back, with no developer hand-holding required. What this PR does NOT do: - No code change. Doc-only. - No new tests. Validation is manual (a person running the app against a real car). - No change to the [needs verification] markers in b58.toml / n55.toml. Those stay until a results PR lands. Verification: - node --test server/dtc/test/ingestor.test.js → all green (no regression) - node --test src/js/histogram.test.js → all green - git diff origin/main...HEAD --stat → 2 files, 305 insertions, 0 deletions (clean; both files new) - This PR does not touch code, workflows, or protected paths. A reviewer with an F/G-series car + ENET adapter is the authoritative verifier. Note on the broken package.json: origin/main's package.json has a missing-comma bug (introduced by a sibling agent in the PR #68/#69 area; noted in PR #70 and #71 bodies). It breaks 'npm run test:*' but does NOT break 'node --test' directly. A separate doc-only PR can fix it. Not fixed here per commit-discipline's 'discovering a broken sibling commit is not license to fix it.' Co-authored-by: ohgeeceee <ohgeeceee@users.noreply.github.com>
This was referenced Jul 15, 2026
github-actions Bot
pushed a commit
that referenced
this pull request
Jul 15, 2026
Continuation of the v0.5.0 close-out pattern. Doc-only. Auto-merge eligible per CLAUDE.md rule 2. What this PR ships: - docs/v0.6.0_plan.md — the proposed v0.6.0 cycle scope and PR sequence. The cycle is named 'Real Hardware' because the work is about turning the now-validated decoder pipeline (v0.3 / v0.4) plus the real-car harness (v0.5.0) into actual tuner-facing workflows on real data. Cycle spine (3 PRs, in order): - PR #1 — Log-merge / comparison (PR #2 in cycle-plan numbering; this is the first v0.6.0 PR). Pure JS / CSS. Adds a 'Compare logs' button next to 'Export CSV' on the Logging tab. Diff-modal shows per-channel meanΔ, std-devΔ, maxΔ, countΔ. ~30 lines of business logic in a new src/js/log_diff.js, ~150 lines of UI. Tested via the existing node --test harness. - PR #2 — Injector duty cycle (decoder + DIDs). Touches src-tauri/src/data/live.rs (new decoder) and the profile TOMLs. Protected path — flag for human review. - PR #3 — OBD-II PID auto-discovery. Pure diagnostic utility (scans standard 0x01 PIDs 0x00..0x7F, reports which respond). The first non-BMW-specific surface shipped via UDS. Touches src-tauri/src/protocol/mod.rs (new scan helper) and src-tauri/src/commands.rs (new #[tauri::command]). Protected path — flag for human review. Out of v0.6.0 scope (deferred per the cycle-plan): The remaining ROADMAP 🟡 items (custom math channels, knock viz polish, AFR polish, adaptation / fuel trim readout polish, trigger-based logging, OBDLink MX+, ENET/DoIP auto-detection, real-car validation B58 / N55 F-series) move to v0.7.0+. All Backlog items (i18n, plugin system, web log viewer, Bootmod3, automatic service manual lookup, OBD-II PID auto-discovery, VIN database) also stay deferred. The plan explicitly notes: - 'No feature without a Discussion' per COMMUNITY_FRAMEWORK.md. This plan is a seed for the Discussion thread, not a substitute for it. No v0.6.0 code should land before the Discussion concludes. - Sibling-agent race in this repo (CLAUDE.md + multi-writer skill): work in fresh sibling clones, branch off origin/main, push from the clone. - origin/main drift (local main was stale during the v0.4 and v0.5 cycles): always git fetch origin before basing a branch, diff against origin/main not main. - CLAUDE.md rule 2: only doc-only PRs auto-merge. PRs #2 and #3 must go through human review. Verification: - node --test server/dtc/test/ingestor.test.js → all green (no regression) - node --test src/js/histogram.test.js → all green - node --test src/js/test/live_format.test.cjs → all green - git diff origin/main...HEAD --stat → 1 file, 210 insertions, 0 deletions (clean; this PR is a new doc file only) - This PR does not touch code, workflows, or protected paths. Co-authored-by: ohgeeceee <ohgeeceee@users.noreply.github.com>
This was referenced Jul 16, 2026
ohgeeceee
added a commit
that referenced
this pull request
Jul 18, 2026
Closing v0.7.0 PR #3 (N20/N26 + S55 profiles) per CLAUDE.md Tier A. All real checks green (rust/python/js/frontend/gate/CodeQL/Analyze); the failing check is a Claude-code-action internal error that posted no review comments. Community data + docs only, no code paths touched.
2 tasks
github-actions Bot
pushed a commit
that referenced
this pull request
Jul 18, 2026
Planning document for the post-v0.7.0 cycle, drafted against main @ ba14141. Docs-only: the plan, plus the ROADMAP/README updates it implies. No code, no data changes. Gap analysis (evidence-level, ISTA+ vs BeeEmUu): - SHIPPED: live data, logging/replay/compare, VIN/vehicle info, freeze-frame decode, transports (K+DCAN, ENET/DoIP + discovery, sim, ISO-TP reassembly). - PARTIAL: DTC coverage (26 built-in texts; 12-address scan table; 6 simulator-grade service functions, none chassis-validated; thin freeze schemas; embryonic guided fault finding). - Broken today: community/dtc_texts.toml truncated mid-string (TOML parse fails, 0 overlay entries load) and CONTRIBUTING.md truncated mid-table — CI can't catch this because lint-toml.js checks whitespace, not parseability. - OUT-OF-SCOPE with reasons: flashing/programming, FSC/AOS, coding writes (this cycle), ISTA repair-doc corpus, immobiliser functions. Four slices: PR #1 data integrity + TOML parse gate (Tier A), PR #2 service-function breadth with [UNVERIFIED] write discipline (Tier B, protected paths flagged), PR #3 B48/S58/N57 profiles (Tier A), PR #4 ECU scan-table breadth + addressing-model doc (Tier A). Each with acceptance criteria and test expectations. ROADMAP.md: v0.7.0 marked merged (PRs #108-110), v0.8.0 active-plan block added, Ready-to-Claim pile pruned of shipped items (theme toggle, workspace, gauge theming, ISO-TP, OBD-II auto-discovery, N20/S55). README.md: "What's coming" refreshed for v0.7.0 merged + v0.8.0 plan link. Flagged for owner (Tier C, not touched): CLAUDE.md invariant notes are stale — keep-alive (#87), ISO-TP (#88), and protocol::read_vin all shipped but still read NOT-YET-IMPLEMENTED. Co-authored-by: ohgeeceee <ohgeeceee@users.noreply.github.com>
9 tasks
ohgeeceee
added a commit
that referenced
this pull request
Jul 18, 2026
Planning document for the post-v0.7.0 cycle, drafted against main @ ba14141. Docs-only: the plan, plus the ROADMAP/README updates it implies. No code, no data changes. Gap analysis (evidence-level, ISTA+ vs BeeEmUu): - SHIPPED: live data, logging/replay/compare, VIN/vehicle info, freeze-frame decode, transports (K+DCAN, ENET/DoIP + discovery, sim, ISO-TP reassembly). - PARTIAL: DTC coverage (26 built-in texts; 12-address scan table; 6 simulator-grade service functions, none chassis-validated; thin freeze schemas; embryonic guided fault finding). - Broken today: community/dtc_texts.toml truncated mid-string (TOML parse fails, 0 overlay entries load) and CONTRIBUTING.md truncated mid-table — CI can't catch this because lint-toml.js checks whitespace, not parseability. - OUT-OF-SCOPE with reasons: flashing/programming, FSC/AOS, coding writes (this cycle), ISTA repair-doc corpus, immobiliser functions. Four slices: PR #1 data integrity + TOML parse gate (Tier A), PR #2 service-function breadth with [UNVERIFIED] write discipline (Tier B, protected paths flagged), PR #3 B48/S58/N57 profiles (Tier A), PR #4 ECU scan-table breadth + addressing-model doc (Tier A). Each with acceptance criteria and test expectations. ROADMAP.md: v0.7.0 marked merged (PRs #108-110), v0.8.0 active-plan block added, Ready-to-Claim pile pruned of shipped items (theme toggle, workspace, gauge theming, ISO-TP, OBD-II auto-discovery, N20/S55). README.md: "What's coming" refreshed for v0.7.0 merged + v0.8.0 plan link. Flagged for owner (Tier C, not touched): CLAUDE.md invariant notes are stale — keep-alive (#87), ISO-TP (#88), and protocol::read_vin all shipped but still read NOT-YET-IMPLEMENTED. Co-authored-by: ohgeeceee <ohgeeceee@users.noreply.github.com>
4 tasks
ohgeeceee
added a commit
that referenced
this pull request
Jul 18, 2026
Three new per-engine profile TOMLs per docs/v0.8.0_plan.md PR #3, repeating the v0.7.0 PR #3 conservative-sourcing pattern: emissions- mandated OBD-II PIDs plus the mirrored OBDb-sourced F-series UDS DID set; no invented DIDs; every UDS entry [needs verification]. - b48.toml (22 params): B48/B46 2.0 turbo modular I4 (G20 330i, G01 X3 30i era). N20-successor clone of the n20.toml set; header documents that nothing in-repo grounds G-series DID applicability, and that oil + fuel trims are omitted for lack of a grounded source. - s58.toml (23 params): S58 twin-turbo I6 (G80/G82/F97/F98 M). S58 is M-tuned B58 architecture, so fuel-trim DIDs 1201/1202 are omitted per the TECH_SPECS-documents-N55-only precedent; keeps the s55 pattern of 7500 rpm / 30.0 MPa display ranges, the UNVERIFIED local:10 oil placeholder (track-use criticality), and ships the BMW M tricolor [profile.theme] block. - n57.toml (30 params): first diesel profile. F-series 3.0 turbo diesel I6 (DDE). Petrol-mirrored set MINUS knock_detect (no knock sensors on compression ignition) and MINUS fuel trims (petrol-only concept); rail-pressure display raised to 250 MPa; oil placeholder kept with a DPF-regen fuel-dilution note. Eight diesel enum DIDs (DPF state/regen/ash/soot, glow plug, NOx state, exhaust temp, EGR cooler) sourced from the DDE candidate catalog in docs/DECODE_FUNCTIONS.md § 8; further catalog candidates (SCR/NH3/ turbo actuator) deliberately held for real-car evidence. community/profiles/README.md shipping table now lists 10 profiles; README.md engine list updated; CHANGELOG has one bullet per profile. Verified: tomllib parses all 19 community TOMLs; lint-toml clean (24 files); cargo build warning-clean; cargo test 99+1 (parse-gate tests cover the new files); node --test 57; pytest 149 pass + 2 known local GIT_CONFIG_* env artifacts. Co-authored-by: ohgeeceee <ohgeeceee@users.noreply.github.com>
ohgeeceee
added a commit
that referenced
this pull request
Jul 18, 2026
…gate (PR #1) (#120) Guided Fault Finding cycle, slice 1 of 5 (Tier A). - docs/testplans.md: the [[step]] schema contract (measurement verbs, on_pass/on_fail/next branches, conclusion nodes, per-step source rule). - community/testplans/README.md: author-facing quick reference. - src-tauri/src/community.rs (test-only): shipped_testplans_branch_integrity (resolvable branches, reachable conclusion, sourced steps, dtc==filename, acyclic BFS) + shipped_oracle_json_parses (survey finding #3: oracle JSON was ungated). - CHANGELOG.md. Gate proven with a temporary broken fixture (dangling branch + unsourced step both caught), then removed. cargo test 102 passed; lint-toml clean. No production code changed. Co-authored-by: Jon currie1 <ohgeeceee@users.noreply.github.com>
ohgeeceee
added a commit
that referenced
this pull request
Jul 19, 2026
…, Tier B) (#122) Guided Fault Finding cycle, slice 3 of 5 (Tier B — protected paths). - src-tauri/src/testplans.rs (new): OnceLock KB mirroring opinions.rs. Loads community/testplans/*.toml at startup, skips malformed/suppressed files, case-insensitive per-DTC query returning Option<TestPlan>. No Rust-side traversal state machine — the branch walk is frontend state, keeping the command surface trivially reviewable. - src-tauri/src/commands.rs (PROTECTED): read-only get_test_plan(dtc_code). - src-tauri/src/lib.rs (PROTECTED): mod testplans + startup load + handler registration + startup log line. - src-tauri/tests/async_commands.rs: get_test_plan added to the sync allowlist with justification (in-memory KB read, same class as get_opinions). Contract change is deliberate and called out. Verification: cargo test 106 lib passed (+4 testplans unit tests) + async_commands allowlist test green + clippy clean. get_test_plan JSON shape: Option<{dtc, title, engine_family, steps:[{id, instruction?, measurement?, on_pass?, on_fail?, next?, conclusion?, source}]}>. Frontend walkthrough UI is PR #4 (next). Protected paths flagged at the top of the PR description per CLAUDE.md Tier B. Co-authored-by: Jon currie1 <ohgeeceee@users.noreply.github.com>
ohgeeceee
added a commit
that referenced
this pull request
Jul 19, 2026
Mounts a branching test-plan walkthrough panel (#walkthrough-panel) beside the opinion / schematics panels in the DTC-detail composition. Clicking a DTC loads its plan via the read-only get_test_plan command (v0.9.0 PR #3) and renders step cards with Pass / Fail / Continue branch buttons, freeze-frame context seeding on the entry step, a breadcrumb of the path taken, and a conclusion card. Branch traversal is a pure, unit-tested reducer (src/js/testplan_walk.js, src/js/test/testplan_walk.test.cjs — 12 tests; full node --test suite now 56 pass). Tier A frontend; no Rust/Python change. Co-authored-by: hermes-agent <ohgeeceee@users.noreply.github.com>
github-actions Bot
pushed a commit
that referenced
this pull request
Jul 19, 2026
ROADMAP v0.9.0 'Guided Fault Finding' moves Planned -> In progress. PRs #1/#2/#3/#4 (#120/#121/#122/#123) marked Done; PR #5 (validation harness + contribution path) remains Ready/Not yet dispatched. Footer refreshed to 2026-07-19. Doc-only, no code change. Tier A per CLAUDE.md. Co-authored-by: hermes-agent <ohgeeceee@users.noreply.github.com>
This was referenced Jul 21, 2026
4 tasks
github-actions Bot
pushed a commit
that referenced
this pull request
Jul 30, 2026
docs/validation/n62-real-car.md: add the three v0.14.3 PIDs (0x5E fuel rate L/h, 0x5F engine runtime s, 0x62 fuel rate g/s) to Step 2 cold-reading + Step 3 running-reading tables. Add critical-row paragraph for fuel-rate failure modes. Extend Step 4 report template + Step 5 consequences. Update cross-references to point at PRs #185/#186/#187 and docs/DECODE_FUNCTIONS.md sections 10-12. ROADMAP.md: close v0.14.3 cycle table (slices 1, 2, 3a, 4 done; slice 3b frontend rewire still open). Bump "Last updated" header. Correct the stale v0.14.2 cycle-table notes that said the deferred PIDs were v0.14.3+ work (they ship in v0.14.3). CHANGELOG.md: add the first entry since v0.14.0 — marked "Unreleased" because slice 3b is still open and the v0.14.3 release cut cannot happen until slice 3b merges. Notes on the version surface explain why the README badge stays at v0.14.0 (CLAUDE.md golden rule #5: don't let the badge lie about an incomplete cycle). Also flags v0.14.1 and v0.14.2 as missing CHANGELOG entries; the maintainer's housekeeping follow-up is the appropriate scope for that backfill. Tier A (docs only). No code changes, no transport/** changes, no protocol/** changes. PR auto-merge eligible per CLAUDE.md once CI is green. Findings flagged (not fixed in this PR — Tier B surface, CLAUDE.md golden rule #3: don't widen PR scope): - src-tauri/src/data/live.rs::tests::remove_param_from_profile_is_idempotent fails on origin/main @ 093b063 (PR #187). Test asserts N-1 params after second remove; returns N. Likely HashSet ordering issue in the test fixture (not the production code path). Worth a separate Tier B fix PR. Co-authored-by: ohgeeceee <ohgeeceee@users.noreply.github.com>
This was referenced Jul 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the cargo-minor-patch group in /src-tauri with 1 update: toml.
Updates
tomlfrom 0.8.2 to 0.8.23Commits
838a022chore: Releaseb9d399ddocs: Update changelogf3e8c68feat(edit): Add ImDocument::into_table (#928)288161bchore: Released7f3cdadocs: Update changelog752ef5bfix(datetime): Further error improvements (#927)32d2297feat(edit): Add ImDocument::into_tableb1ce9b5fix(datetime): Use 2-digit values for ranges55da4affix(datetime): Remove trailing space in error5c1d9ccchore(parse): Use a unique tagDependabot 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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions